Triple
T23959894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seychelles Time |
E603895
|
entity |
| Predicate | timeStandardBase |
P34615
|
FINISHED |
| Object | Coordinated Universal Time |
—
|
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: Coordinated Universal Time | Statement: [Seychelles Time, timeStandardBase, Coordinated Universal Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeStandardBase Context triple: [Seychelles Time, timeStandardBase, Coordinated Universal Time]
-
A.
timingStandard
Indicates that one entity specifies or conforms to the timing rules, constraints, or reference schedule defined by another entity.
-
B.
timeScaleStandard
chosen
Indicates the standard or convention used to define, measure, or interpret the time scale associated with an event or process.
-
C.
standardTimeType
Indicates that a time value is expressed using a particular standard or conventional time format or classification.
-
D.
timeAdvanceFromStandard
Indicates that one time value represents an advancement or offset forward from a defined standard or reference time.
-
E.
timeSystem
Indicates a relationship where an entity uses, follows, or is defined within a particular system for measuring or organizing time.
- 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_69e2954222288190a7323554d0cca8d7 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0d91cd481908f53ce7ee569c0f9 |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:23 p.m.