Triple
T38655367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Final Fantasy XIV: Endwalker |
E939876
|
entity |
| Predicate | addsMajorHub |
P191481
|
FINISHED |
| Object | Radz-at-Han |
—
|
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: Radz-at-Han | Statement: [Final Fantasy XIV: Endwalker, addsMajorHub, Radz-at-Han]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsMajorHub Context triple: [Final Fantasy XIV: Endwalker, addsMajorHub, Radz-at-Han]
-
A.
connectsMajorHub
Indicates that one entity serves as a link or route between major hubs or primary nodes in a network.
-
B.
hasMajorHubIn
Indicates that an entity maintains a primary or significant operational hub or center in a specified location.
-
C.
isMajorHubType
Indicates that an entity functions as a primary or central hub within a larger network or system.
-
D.
isMajorTransferHubIn
Indicates that a location functions as a primary node where significant volumes of transfers or connections occur within a specified area or network.
-
E.
majorHubServed
Indicates that a major transportation or logistical hub is served or connected by a particular route, service, or facility.
- 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.