Triple
T38590428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eorzea |
E932439
|
entity |
| Predicate | hasTimeSystem |
P15775
|
FINISHED |
| Object | Eorzean time |
—
|
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: Eorzean time | Statement: [Eorzea, hasTimeSystem, Eorzean time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeSystem Context triple: [Eorzea, hasTimeSystem, Eorzean time]
-
A.
usesClockSystem
Indicates that one entity employs or operates according to the clock or timekeeping system defined or provided by another entity.
-
B.
timeSystem
chosen
Indicates a relationship where an entity uses, follows, or is defined within a particular system for measuring or organizing time.
-
C.
hasClock
Indicates that one entity possesses, contains, or is equipped with a clock.
-
D.
hasTimeIndication
Indicates that something includes, specifies, or is associated with a particular time-related indication (such as a timestamp, time period, or temporal marker).
-
E.
hasTimeComponent
Indicates that something includes, is associated with, or is characterized by a specific temporal aspect or time-related element.
- 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_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: May 3, 2026, 4:32 p.m.