Triple
T30633115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Seven Rings for the Dwarf-lords |
E779762
|
entity |
| Predicate | intendedBearers |
P190497
|
FINISHED |
| Object | Dwarf-lords |
—
|
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: Dwarf-lords | Statement: [The Seven Rings for the Dwarf-lords, intendedBearers, Dwarf-lords]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedBearers Context triple: [The Seven Rings for the Dwarf-lords, intendedBearers, Dwarf-lords]
-
A.
typicalBearers
Indicates that certain entities are the usual or characteristic holders, users, or possessors of a given property, role, or attribute.
-
B.
hasMultipleBearers
Indicates that a single item, attribute, or role is associated with more than one bearer or holder simultaneously.
-
C.
hasAlternativeBearers
Indicates that an entity can be carried, represented, or borne by more than one possible bearer or carrier as alternatives.
-
D.
primaryBearer
Indicates that an entity serves as the main or principal holder, carrier, or responsible agent for another entity or attribute.
-
E.
intendedCarrier
Indicates that one entity is designated or planned to serve as the carrier or transporter of another entity.
- F. None of above. chosen
Provenance (4 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcc7779d248190afdb348a95375443 |
completed | May 7, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
| PDg | Predicate description generation | batch_69fcc73264e08190b0b5917f32226fae |
completed | May 7, 2026, 5:09 p.m. |
Created at: April 29, 2026, 8:28 p.m.