Triple
T27612368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Protocol |
E700358
|
entity |
| Predicate | maximumRepresentableTimeSpan |
P165333
|
FINISHED |
| Object | 2^32 seconds |
—
|
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: 2^32 seconds | Statement: [Time Protocol, maximumRepresentableTimeSpan, 2^32 seconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumRepresentableTimeSpan Context triple: [Time Protocol, maximumRepresentableTimeSpan, 2^32 seconds]
-
A.
maximumExtentTime
Indicates the specific time at which something reaches its greatest extent, magnitude, or intensity.
-
B.
maximumPeriod
chosen
Indicates that there is an upper bound on the duration or time interval for which a given condition, state, or relationship can hold.
-
C.
largestSpan
Indicates that the referenced entity has the greatest extent or coverage (in distance, time, or range) among a set of comparable spans.
-
D.
maximumRecordedLifespan
Indicates the greatest length of time that has ever been recorded for an individual of a given type to live.
-
E.
maximumExtent
Indicates the greatest or furthest degree, size, or range to which something can extend or apply within a given context.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 2:11 p.m.