Triple
T34553244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saavedra, Buenos Aires |
E887130
|
entity |
| Predicate | servedByBusLines |
P39381
|
FINISHED |
| Object | multiple city bus lines |
—
|
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: multiple city bus lines | Statement: [Saavedra, Buenos Aires, servedByBusLines, multiple city bus lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByBusLines Context triple: [Saavedra, Buenos Aires, servedByBusLines, multiple city bus lines]
-
A.
servedByBusCorridor
Indicates that a location or route is provided public transport service by a specific bus corridor.
-
B.
servedByTramwayLine
Indicates that a location or area is provided public transport service by a specific tramway line.
-
C.
transportationServedBy
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
-
D.
hasBusServices
chosen
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
-
E.
isPublicTransportBackboneOf
Indicates that one transport system serves as the primary structural and functional core of a region’s overall public transportation network.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffc083a54c8190ac80d05ee8d20a6b |
completed | May 9, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69ffbfeb05b88190b4d50ce8124004d9 |
completed | May 9, 2026, 11:14 p.m. |
Created at: May 1, 2026, 2:02 a.m.