Triple
T27612367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Protocol |
E700358
|
entity |
| Predicate | supportsDateInfo |
P199870
|
FINISHED |
| Object | implicitly via seconds since epoch |
—
|
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: implicitly via seconds since epoch | Statement: [Time Protocol, supportsDateInfo, implicitly via seconds since epoch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDateInfo Context triple: [Time Protocol, supportsDateInfo, implicitly via seconds since epoch]
-
A.
supportsDateRestrictions
Indicates that an entity can enforce or handle constraints based on specific dates or date ranges.
-
B.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
C.
integratedDate
Indicates the date on which one entity was incorporated, combined, or brought into a larger system or whole.
-
D.
hasDateContext
Indicates that something is associated with, constrained by, or interpreted within a specific date or time-related context.
-
E.
dateDetermination
Indicates the process or criteria by which a specific date is identified, calculated, or assigned in relation to an event or condition.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
| PDg | Predicate description generation | batch_69ff607407a881909d9e6e1c98559a6e |
completed | May 9, 2026, 4:27 p.m. |
Created at: April 27, 2026, 2:11 p.m.