Triple
T23690231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro Ligero Line ML3 |
E585276
|
entity |
| Predicate | isPartOfTransportZone |
P17300
|
FINISHED |
| Object | Madrid fare zones |
—
|
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 fare zones | Statement: [Metro Ligero Line ML3, isPartOfTransportZone, Madrid fare zones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfTransportZone Context triple: [Metro Ligero Line ML3, isPartOfTransportZone, Madrid fare zones]
-
A.
locatedInTransportArea
Indicates that an entity is situated within a designated transport-related area or zone.
-
B.
publicTransportZone
chosen
Indicates that an entity is located within, associated with, or valid for a specific public transportation fare or service zone.
-
C.
locatedInTravelcardZoneBoundary
Indicates that something lies on or within the defined boundary of a specific travelcard fare zone.
-
D.
fareZoneIncludes
Indicates that a specified fare zone geographically or logically contains a given location, stop, or segment for fare calculation purposes.
-
E.
hasRailwayZone
Indicates that a location or railway entity falls under the jurisdiction or coverage area of a specific railway zone.
- 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b5c16af08190b2f4d126c60a7e75 |
completed | April 29, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:52 p.m.