Triple
T38590644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyur |
E932444
|
entity |
| Predicate | isWidespreadIn |
P22713
|
FINISHED |
| Object | Eorzea |
—
|
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: Eorzea | Statement: [Hyur, isWidespreadIn, Eorzea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWidespreadIn Context triple: [Hyur, isWidespreadIn, Eorzea]
-
A.
isEndemicTo
Indicates that something naturally occurs and is restricted to a particular geographic area or region.
-
B.
prevalentIn
chosen
Indicates that something occurs frequently or is commonly found within a particular context, group, or environment.
-
C.
countryOrRegionOfPrevalence
Indicates the country or geographic region where something (such as a condition, practice, or phenomenon) is most commonly found or occurs most frequently.
-
D.
hasGlobalDistribution
Indicates that the related entity occurs, operates, or is present across most or all regions of the world rather than being confined to a specific locality or region.
-
E.
isReservoirOf
Indicates that one entity serves as a storage source or container holding a particular substance, resource, or quantity for another entity or purpose.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.