Triple
T22422899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sext |
E554293
|
entity |
| Predicate | correspondsToHour |
P148114
|
FINISHED |
| Object | sixth hour of the day |
—
|
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: sixth hour of the day | Statement: [Sext, correspondsToHour, sixth hour of the day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correspondsToHour Context triple: [Sext, correspondsToHour, sixth hour of the day]
-
A.
isWholeHourOffset
Indicates that the time zone or time offset differs from a reference time (typically UTC) by an exact whole number of hours, with no fractional minutes involved.
-
B.
isMajorHourIn
Indicates that a given hour is a major or significant hour within a specified time period, schedule, or context.
-
C.
isThreeQuartersOfAnHourAheadOf
Indicates that one entity’s time occurs exactly 45 minutes later than the other entity’s time.
-
D.
hasMatchMinute
Indicates the specific minute within a match at which an associated event or action occurs.
-
E.
isNinetyMinutesAheadOf
Indicates that one entity occurs or is positioned exactly ninety minutes later in time than another 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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a2a1a3c8190a649ee4df2429e69 |
completed | April 29, 2026, 1:08 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:47 p.m.