Triple
T13440241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beaver |
E320339
|
entity |
| Predicate | historicallyHuntedFor |
P16288
|
FINISHED |
| Object | fur |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: fur | Statement: [Beaver, historicallyHuntedFor, fur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyHuntedFor Context triple: [Beaver, historicallyHuntedFor, fur]
-
A.
historicallySoughtAs
Indicates that one entity has been pursued, desired, or actively sought by another entity over a historical period or in past contexts.
-
B.
historicallySoughtBy
chosen
Indicates that one entity has been actively pursued, desired, or searched for by another entity in the past.
-
C.
historicalFate
Indicates that two entities share a common or interconnected outcome, destiny, or consequence within a historical context.
-
D.
historicallyRich
Indicates that an entity possesses significant historical depth, importance, or a wealth of notable past events and heritage.
-
E.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaee704ac8190b4c7f4e0d3a88494 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.