Triple
T73041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 1588 Precision Time Protocol standard |
E1462
|
entity |
| Predicate | firstEditionYear |
P25
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [IEEE 1588 Precision Time Protocol standard, firstEditionYear, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEditionYear Context triple: [IEEE 1588 Precision Time Protocol standard, firstEditionYear, 2002]
-
A.
publicationYear
chosen
Indicates the specific calendar year in which a work was formally published or released.
-
B.
firstCelebratedInYear
Indicates the year in which something (such as an event, holiday, or celebration) was first observed or celebrated.
-
C.
wasFirstBuiltInYear
Indicates that the initial construction of an entity was completed in a specified year.
-
D.
firstOfficialClaimYear
Indicates the year in which an entity was first officially claimed, recorded, or recognized in an authoritative capacity.
-
E.
introducedInYear
Indicates the year in which something was first introduced, launched, or made available.
- 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a252201fa481908e30791954119c17 |
completed | Feb. 28, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69a24eacfdc481909e9ff99752fd42bf |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.