Triple
T23763451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EMT Madrid |
E587312
|
entity |
| Predicate | operatesBusFleet |
P81300
|
FINISHED |
| Object | Madrid municipal bus fleet |
—
|
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: Madrid municipal bus fleet | Statement: [EMT Madrid, operatesBusFleet, Madrid municipal bus fleet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesBusFleet Context triple: [EMT Madrid, operatesBusFleet, Madrid municipal bus fleet]
-
A.
operatesSchoolBuses
Indicates that an entity is responsible for running or managing the operation of school bus services for transporting students.
-
B.
operatesTransitSystem
chosen
Indicates that one entity manages and runs the public transportation network or services for another entity or area.
-
C.
operatesInterurbanBusServices
Indicates that an entity runs or manages bus transportation services operating between different towns or cities within a region.
-
D.
operatedPassengerServices
Indicates that an entity provided and managed transportation services specifically for carrying passengers.
-
E.
hasBusOperator
Indicates that a bus service, route, or vehicle is operated or managed by a specific operator or company.
- 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bdb40ee881908f3916cc6d05fc72 |
completed | April 29, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:14 p.m.