Triple
T9399603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dwarves of Erebor |
E226432
|
entity |
| Predicate | statusAfterSmaug |
P88730
|
FINISHED |
| Object | exiled |
—
|
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: exiled | Statement: [Dwarves of Erebor, statusAfterSmaug, exiled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterSmaug Context triple: [Dwarves of Erebor, statusAfterSmaug, exiled]
-
A.
protagonistStatusAfterSleep
Indicates the condition or state of the main character immediately following a period of sleep.
-
B.
titleAfterSurrender
Indicates that one entity holds a title or designation that was granted or recognized only after a surrender, capitulation, or yielding event involving another entity.
-
C.
handledAftermathOf
Indicates that one entity took responsibility for dealing with the consequences or fallout that occurred after another entity’s actions or events.
-
D.
statusAfterExile
Indicates the condition or standing an entity has once a period of exile has ended.
-
E.
saidToBeTheLast
Indicates that something or someone is claimed or reported to be the final instance or member in a sequence, series, or group.
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5156b9588190bafb6b1c3ee3c0ed |
completed | April 1, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:46 p.m.