Triple
T37094364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Realms of Arnor and Gondor |
E918518
|
entity |
| Predicate | capitalOfGondor |
P59230
|
FINISHED |
| Object | Osgiliath |
E271243
|
NE 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: Osgiliath | Statement: [Realms of Arnor and Gondor, capitalOfGondor, Osgiliath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOfGondor Context triple: [Realms of Arnor and Gondor, capitalOfGondor, Osgiliath]
-
A.
isShireSeatOf
Indicates that a location serves as the administrative center or county town (shire seat) for a given shire or county.
-
B.
capitalOfCoronationEmpire
Indicates that a city or location serves as the capital of the Coronation Empire.
-
C.
capitalOfHisKingdom
chosen
Indicates that one entity serves as the capital city of the kingdom ruled or possessed by another entity.
-
D.
portCityOfRealm
Indicates that a city serves as a primary seaport or harbor for a particular realm, such as a country, kingdom, or region.
-
E.
neighbourCitySindarinName
Indicates that the Sindarin-language name of a city is associated with another city that is geographically adjacent or considered a neighbor.
- F. None of above.
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_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40cd9f2cd88190a092060977c8936d |
completed | June 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: May 3, 2026, 4:14 p.m.