Triple
T2484685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITU-T G.8272 |
E55896
|
entity |
| Predicate | typeOfClockDefined |
P17358
|
FINISHED |
| Object | primary reference time 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: primary reference time clock | Statement: [ITU-T G.8272, typeOfClockDefined, primary reference time clock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfClockDefined Context triple: [ITU-T G.8272, typeOfClockDefined, primary reference time clock]
-
A.
hasClock
Indicates that one entity possesses, contains, or is equipped with a clock.
-
B.
clockType
chosen
Indicates the type or category of a clock associated with an entity (e.g., analog, digital, system clock, etc.).
-
C.
usesClockSystem
Indicates that one entity employs or operates according to the clock or timekeeping system defined or provided by another entity.
-
D.
hasClockTower
Indicates that one entity possesses or features a clock tower as part of its structure or property.
-
E.
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).
- 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_69ab49e670a88190b928e08302381710 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd20b6d008190acec0eb172e218c9 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b7cf088190bcff4dac6150044c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.