Triple
T38655373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Final Fantasy XIV: Endwalker |
E939876
|
entity |
| Predicate | addsDungeonType |
P188692
|
FINISHED |
| Object | leveling dungeons |
—
|
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: leveling dungeons | Statement: [Final Fantasy XIV: Endwalker, addsDungeonType, leveling dungeons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsDungeonType Context triple: [Final Fantasy XIV: Endwalker, addsDungeonType, leveling dungeons]
-
A.
addsPublicDungeon
Indicates that an entity introduces or includes a public dungeon as part of its content or structure.
-
B.
dungeonType
chosen
Indicates the specific category or kind of dungeon associated with an entity or location.
-
C.
addsNPCType
Indicates that one entity introduces or registers a specific type of non-player character (NPC) into a system, context, or environment.
-
D.
addsDelves
Indicates that one entity performs the action of adding or appending something to another entity in a detailed or exploratory manner.
-
E.
addsFeatureType
Indicates that one entity introduces or incorporates a specific feature type into another entity or system.
- 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_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. |
Created at: May 3, 2026, 4:33 p.m.