Triple
T3995898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montreal bus network |
E87096
|
entity |
| Predicate | hasServicePeriod |
P44456
|
FINISHED |
| Object | peak hours |
—
|
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: peak hours | Statement: [Montreal bus network, hasServicePeriod, peak hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServicePeriod Context triple: [Montreal bus network, hasServicePeriod, peak hours]
-
A.
hasWorkPeriod
chosen
Indicates that an entity is associated with a specific span of time during which it performs or is engaged in some work or activity.
-
B.
hasInceptionPeriod
Indicates the time span or period during which something begins or comes into existence.
-
C.
eligibilityPeriod
Indicates the span of time during which an entity qualifies for or is allowed to receive a particular benefit, service, or status.
-
D.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
E.
hasCountingPeriod
Indicates that there is a defined time span or interval over which occurrences, quantities, or measurements related to an entity are counted or aggregated.
- 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_69aed94118148190975e6aa4e554cde9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb81040481909b22e4c445ecae0f |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef8f692008190bf4d637ffc3d3eaa |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:34 p.m.