Triple
T37539620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Final Fantasy XIV: Heavensward |
E933291
|
entity |
| Predicate | addsAreaType |
P6822
|
FINISHED |
| Object | floating islands |
—
|
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: floating islands | Statement: [Final Fantasy XIV: Heavensward, addsAreaType, floating islands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsAreaType Context triple: [Final Fantasy XIV: Heavensward, addsAreaType, floating islands]
-
A.
hasAreaType
chosen
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
-
B.
includesAreaType
Indicates that one entity encompasses or contains another entity of a specified area type within its scope or boundaries.
-
C.
typeOfAreaRepresented
Indicates that one entity specifies the kind or category of area that another entity represents.
-
D.
addsRegion
Indicates that one entity expands or augments another by including an additional geographic or spatial region.
-
E.
connectsTypeOfAreas
Indicates a relationship where one entity serves as a link or connector between two different types of areas.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.