Triple
T38655366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Final Fantasy XIV: Endwalker |
E939876
|
entity |
| Predicate | addsCityState |
P191480
|
FINISHED |
| Object | Old Sharlayan |
—
|
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: Old Sharlayan | Statement: [Final Fantasy XIV: Endwalker, addsCityState, Old Sharlayan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsCityState Context triple: [Final Fantasy XIV: Endwalker, addsCityState, Old Sharlayan]
-
A.
containsCityState
Indicates that one entity includes or encompasses a specific city and state within its scope or boundaries.
-
B.
associatedCityState
Indicates a relationship where a city is linked to the state with which it is formally or contextually connected.
-
C.
isCityState
Indicates that one entity is a city located within, and politically or administratively belonging to, the state represented by the other entity.
-
D.
governingCityState
Indicates that one city or state holds governing authority or administrative control over another specified region or entity.
-
E.
belongsToCityState
Indicates that an entity is located within or associated with a specific city and state jurisdiction.
- 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_69f76ede49648190a48bfe47032a05a3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdfbafbf48190abe38ec0003a6419 |
completed | May 7, 2026, 6:53 p.m. |
Created at: May 3, 2026, 4:33 p.m.