Triple
T3422912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MTD |
E72153
|
entity |
| Predicate | serviceSpan |
P17164
|
FINISHED |
| Object | daytime service |
—
|
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: daytime service | Statement: [MTD, serviceSpan, daytime service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceSpan Context triple: [MTD, serviceSpan, daytime service]
-
A.
serviceDuring
Indicates that one entity performs or provides a service for another entity during a specified time period or event.
-
B.
serviceEntryPeriod
chosen
Indicates the span of time during which a service is active, valid, or in effect for the related entities.
-
C.
serviceContinuationEra
Indicates the historical or temporal period during which a service continues to operate or remain in effect.
-
D.
serviceAge
Indicates the length of time an entity has been in service or actively performing its role.
-
E.
serviceExtendedTo
Indicates that a service has been made available or expanded to include a particular entity, location, or group.
- 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb95223e081908b2954769d2f46c8 |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.