Triple
T38542284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCTS |
E924864
|
entity |
| Predicate | hasServiceTimeCharacteristic |
P99305
|
FINISHED |
| Object | daily service on most routes |
—
|
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: daily service on most routes | Statement: [MCTS, hasServiceTimeCharacteristic, daily service on most routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceTimeCharacteristic Context triple: [MCTS, hasServiceTimeCharacteristic, daily service on most routes]
-
A.
hasServiceTime
chosen
Indicates that an entity is associated with a specific duration or schedule during which a service is provided.
-
B.
hasDurationCharacteristic
Indicates that something possesses a specific temporal property, such as length, span, or persistence over time.
-
C.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
D.
servedTimeIn
Indicates that an entity spent or completed a specified duration of time within a particular place, context, or role.
-
E.
servedTimeFor
Indicates that one entity has completed or spent a specified duration of time serving a sentence, obligation, or term on behalf of another entity or for a particular case or offense.
- 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00d76d0e0881908d83a8dcce511167 |
completed | May 10, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_6a00d711805881909a94cfd1f25fb331 |
completed | May 10, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:32 p.m.