Triple
T19243225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National City Lines |
E481181
|
entity |
| Predicate | peakNumberOfSystemsOperated |
P135326
|
FINISHED |
| Object | over 40 local transit systems |
—
|
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: over 40 local transit systems | Statement: [National City Lines, peakNumberOfSystemsOperated, over 40 local transit systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakNumberOfSystemsOperated Context triple: [National City Lines, peakNumberOfSystemsOperated, over 40 local transit systems]
-
A.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
-
B.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
C.
oftenOperatedBy
Indicates that an entity is frequently or typically operated, controlled, or run by another entity.
-
D.
servedSystem
Indicates that one system has provided service, functionality, or resources to another system.
-
E.
operatedSince
Indicates that an entity has been in operation continuously from a specified starting time or date.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5faf3018881909ef866616c45ff2e |
completed | April 20, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4debc39ac81908b7c5ef797046360 |
completed | April 19, 2026, 1:55 p.m. |
Created at: April 10, 2026, 1:27 p.m.