Triple
T37591738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Final Fantasy XIV: Stormblood |
E935275
|
entity |
| Predicate | addsBeastTribe |
P100010
|
FINISHED |
| Object | Ananta |
—
|
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: Ananta | Statement: [Final Fantasy XIV: Stormblood, addsBeastTribe, Ananta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsBeastTribe Context triple: [Final Fantasy XIV: Stormblood, addsBeastTribe, Ananta]
-
A.
introducedTribe
chosen
Indicates that one entity caused a tribe to become known, present, or established to another entity or context for the first time.
-
B.
tribeInteractedWith
Indicates that a tribe has engaged in some form of interaction or contact with another entity.
-
C.
recognizedTribe
Indicates that a group is officially acknowledged as a tribe by a governing or authoritative body.
-
D.
associatedTribeLocation
Indicates a relationship where a tribe is linked or connected to a specific geographic location.
-
E.
tribeName
Indicates the name assigned to a tribe in the relationship.
- 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.