Triple
T33112546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kings of Arthedain |
E847368
|
entity |
| Predicate | usedHeirloom |
P28796
|
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 Arthedain, usedHeirloom, Ring of Barahir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedHeirloom Context triple: [Kings of Arthedain, usedHeirloom, Ring of Barahir]
-
A.
usedByHeir
Indicates that something is utilized or employed by an heir.
-
B.
hasHeirloom
Indicates that one entity possesses or is associated with an heirloom originating from another entity.
-
C.
usedItem
chosen
Indicates that an entity has utilized or employed a particular item for some purpose.
-
D.
usedOver
Indicates that one entity has been utilized, applied, or consumed in relation to another entity, typically as a resource, medium, or tool in a particular context or period.
-
E.
usedOrb
Indicates that an entity made use of or employed an orb to perform an action or achieve some effect.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:27 a.m.