Triple
T9399576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dwarves of Erebor |
E226432
|
entity |
| Predicate | exiledInYear |
P36602
|
FINISHED |
| Object | T.A. 2770 |
—
|
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: T.A. 2770 | Statement: [Dwarves of Erebor, exiledInYear, T.A. 2770]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exiledInYear Context triple: [Dwarves of Erebor, exiledInYear, T.A. 2770]
-
A.
expulsionYear
chosen
Indicates the year in which an entity was formally expelled or removed from a group, institution, or place.
-
B.
wasExiled
Indicates that an entity was forcibly sent away from their home or country, typically as a punishment or due to political or social pressures.
-
C.
livedInExileIn
Indicates that an entity spent a period of time living outside its home country or usual place of residence due to exile, in a specified location.
-
D.
yearOfEmigration
Indicates the specific year in which an entity permanently left its country or place of origin to settle elsewhere.
-
E.
traditionallyExiledTo
Indicates that an entity has, by long-standing custom or tradition, been sent away or banished to a particular place.
- 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_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. |
Created at: March 30, 2026, 7:46 p.m.