Triple
T37094363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Realms of Arnor and Gondor |
E918518
|
entity |
| Predicate | laterCapitalOfArnor |
P202891
|
FINISHED |
| Object | Fornost Erain |
—
|
NE NERFINISHED |
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: Fornost Erain | Statement: [Realms of Arnor and Gondor, laterCapitalOfArnor, Fornost Erain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterCapitalOfArnor Context triple: [Realms of Arnor and Gondor, laterCapitalOfArnor, Fornost Erain]
-
A.
neighbourCitySindarinName
Indicates that the Sindarin-language name of a city is associated with another city that is geographically adjacent or considered a neighbor.
-
B.
predecessorDynastyInArnor
Indicates that one dynasty historically preceded and was replaced by another within the realm of Arnor.
-
C.
isShireSeatOf
Indicates that a location serves as the administrative center or county town (shire seat) for a given shire or county.
-
D.
Listoghil
Indicates a relationship in which an entity is associated with or belongs to the place or context referred to as Listoghil.
-
E.
enteredBeleriand
Indicates that an entity moved into or came within the region or realm referred to as Beleriand.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00cbae75988190974f5b45a2e62326 |
completed | May 10, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_6a00cabe4c5881909cca5efbe494e0d1 |
completed | May 10, 2026, 6:13 p.m. |
| PDg | Predicate description generation | batch_6a00cbad83e88190ba792d3172370f63 |
completed | May 10, 2026, 6:17 p.m. |
Created at: May 3, 2026, 4:14 p.m.