Triple
T33217165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longbeards |
E850318
|
entity |
| Predicate | statusAmongDwarves |
P176214
|
FINISHED |
| Object | eldest of the Seven Houses 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: eldest of the Seven Houses of the Dwarves | Statement: [Longbeards, statusAmongDwarves, eldest of the Seven Houses of the Dwarves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAmongDwarves Context triple: [Longbeards, statusAmongDwarves, eldest of the Seven Houses of the Dwarves]
-
A.
hasNumberOfDwarves
Indicates that an entity is associated with a specific count of dwarves.
-
B.
consideredByElves
Indicates that something is regarded, judged, or held in a particular way by elves.
-
C.
includesDwarf
Indicates that something contains or features at least one dwarf as part of its composition, membership, or elements.
-
D.
oneOfSevenHousesOfDwarves
chosen
Indicates that something belongs to or is associated with one of the seven houses (lineages or clans) of the Dwarves.
-
E.
rankAmongGods
Indicates how a being’s status or position compares relative to other gods within a divine hierarchy.
- 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_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
Created at: May 1, 2026, 1:30 a.m.