Triple
T17444859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QLine |
E424753
|
entity |
| Predicate | hasHeadway |
P22511
|
FINISHED |
| Object | shorter headways during peak periods |
—
|
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: shorter headways during peak periods | Statement: [QLine, hasHeadway, shorter headways during peak periods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeadway Context triple: [QLine, hasHeadway, shorter headways during peak periods]
-
A.
headway
chosen
Indicates the temporal or spatial separation maintained between moving entities, such as vehicles or trains, as they travel along the same route.
-
B.
hasHeadCount
Indicates that an entity is associated with a specific number of individuals, typically representing the size or count of people (or similar units) related to it.
-
C.
hasHeadOf
Indicates that one entity serves as the leader, chief, or person in charge of another entity (such as an organization, group, or department).
-
D.
hasTrail
Indicates that an entity possesses, includes, or is associated with a trail or pathway.
-
E.
hasCadence
Indicates that something possesses or exhibits a particular rhythmic pattern, tempo, or flow.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44ffa2d84819086474649eba1065c |
completed | April 19, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.