Triple
T17690366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FKST |
E441007
|
entity |
| Predicate | offsetUnit |
P128585
|
FINISHED |
| Object | hour |
—
|
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: hour | Statement: [FKST, offsetUnit, hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offsetUnit Context triple: [FKST, offsetUnit, hour]
-
A.
offsetSeconds
Indicates a temporal relationship where one event or time point occurs a specified number of seconds before or after another reference time.
-
B.
coordinateUnit
Indicates that one unit serves as a coordinate or reference unit relative to another in a measurement, spatial, or organizational context.
-
C.
minorUnitExponent
Indicates the power-of-ten exponent that defines how a minor unit relates in scale to its corresponding major unit.
-
D.
offsetInSecondsFromUTC
Indicates the time difference, measured in whole seconds, between a given time reference and Coordinated Universal Time (UTC).
-
E.
offsetFrom
Indicates that one entity is positioned or scheduled at a specific distance, time, or value away from another reference entity.
- F. None of above. chosen
Provenance (4 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4704b43a88190ba29654ca695839e |
completed | April 19, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 10:03 a.m.