Triple
T33381555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kings of Gondor |
E854795
|
entity |
| Predicate | usesHeirloom |
P20494
|
FINISHED |
| Object | Ring of Barahir |
—
|
NE NERFINISHED |
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: Ring of Barahir | Statement: [Kings of Gondor, usesHeirloom, Ring of Barahir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHeirloom Context triple: [Kings of Gondor, usesHeirloom, Ring of Barahir]
-
A.
hasHeirloom
chosen
Indicates that one entity possesses or is associated with an heirloom originating from another entity.
-
B.
usedByHeir
Indicates that something is utilized or employed by an heir.
-
C.
usesLegacyOf
Indicates that one entity makes use of, builds upon, or derives benefit from the historical work, reputation, or established influence of another entity.
-
D.
coHeirWith
Indicates that two or more entities jointly inherit or share rights to the same estate, title, or legacy.
-
E.
usesHallOf
Indicates that one entity makes use of or operates within the hall or hall-like facility 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_69f3496ca10c8190908640d18fa00832 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:35 a.m.