Triple

T37591744
Position Surface form Disambiguated ID Type / Status
Subject Final Fantasy XIV: Stormblood E935275 entity
Predicate includesCity P3207 FINISHED
Object Kugane
Kugane is a bustling, isolationist port city in Final Fantasy XIV known for its Far Eastern architecture, strict laws, and role as a major hub in the Stormblood expansion.
E2296089 NE 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: Kugane | Statement: [Final Fantasy XIV: Stormblood, includesCity, Kugane]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Kugane
Triple: [Final Fantasy XIV: Stormblood, includesCity, Kugane]
Generated description
Kugane is a bustling, isolationist port city in Final Fantasy XIV known for its Far Eastern architecture, strict laws, and role as a major hub in the Stormblood expansion.

Provenance (5 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_69fba8be7e1c819084874919eecdc02d completed May 6, 2026, 8:46 p.m.
NED1 Entity disambiguation (via context triple) batch_6a823185baac8190be14244cc6556a66 completed Aug. 16, 2026, 9:54 p.m.
NEDg Description generation batch_6a8231d719c08190ab9a5d09956b2ce9 completed Aug. 16, 2026, 9:55 p.m.
NED2 Entity disambiguation (via description) batch_6a82322937d481908c7211dcd6d87714 completed Aug. 16, 2026, 9:56 p.m.
Created at: May 3, 2026, 4:18 p.m.