Triple
T33217204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longbeards |
E850318
|
entity |
| Predicate | heldDwarvenRing |
P84120
|
FINISHED |
| Object | one of the Seven Rings of the Dwarves |
—
|
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: one of the Seven Rings of the Dwarves | Statement: [Longbeards, heldDwarvenRing, one of the Seven Rings of the Dwarves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldDwarvenRing Context triple: [Longbeards, heldDwarvenRing, one of the Seven Rings of the Dwarves]
-
A.
rankAmongElvenRings
Indicates the relative position or status of an item within the hierarchy or ordering of the Elven Rings.
-
B.
ringNameForOneRing
Indicates that a given name is the specific title or designation used for the One Ring.
-
C.
ElrondChose
Indicates that Elrond made a deliberate selection or decision regarding a particular option, entity, or course of action.
-
D.
hasRingComposition
Indicates that one entity is composed of, or structurally organized around, a ring-like arrangement or circular structure.
-
E.
hasRing
chosen
Indicates that one entity possesses, wears, or is characterized by the presence of a ring.
- 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:30 a.m.