Triple
T25955364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NTV |
E654078
|
entity |
| Predicate | operatesInTimeFormat |
P2162
|
FINISHED |
| Object | 24-hour clock |
—
|
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: 24-hour clock | Statement: [NTV, operatesInTimeFormat, 24-hour clock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesInTimeFormat Context triple: [NTV, operatesInTimeFormat, 24-hour clock]
-
A.
operatesAtTime
Indicates that an action, process, or system is functioning or active during a specified time or time interval.
-
B.
timeNotation
chosen
Indicates the specific system or format used to represent and write times (e.g., 12-hour vs 24-hour notation).
-
C.
representsTimeIn
Indicates that one entity expresses, encodes, or specifies the time at which another entity occurs, is valid, or is observed.
-
D.
timeType
Indicates the specific temporal category or classification associated with a time-related entity or value (e.g., duration, point in time, interval, or recurrence type).
-
E.
operatesAllTimes
Indicates that the action, service, or process is continuously in operation at all times without interruption.
- 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 22, 2026, 8:44 a.m.