Triple
T24394736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonia Nápoles |
E614996
|
entity |
| Predicate | hasNearbyMetrobusLine |
P34620
|
FINISHED |
| Object | Metrobús Line 1 |
—
|
NE NERFINISHED |
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: Metrobús Line 1 | Statement: [Colonia Nápoles, hasNearbyMetrobusLine, Metrobús Line 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyMetrobusLine Context triple: [Colonia Nápoles, hasNearbyMetrobusLine, Metrobús Line 1]
-
A.
hasNearbyTramStop
Indicates that a location has a tram stop situated within a short walking distance or close proximity.
-
B.
hasPublicTransportStop
Indicates that a location or area contains or is served by a public transport stop, such as a bus, tram, or train stop.
-
C.
operatorOfNearbyTransit
Indicates that an entity operates or manages a public transit service located in close geographic proximity to another specified entity.
-
D.
hasAdjacentBusStation
Indicates that one location has a bus station situated directly next to or very near it.
-
E.
hasPublicTransitRoute
chosen
Indicates that there exists a public transportation route (such as a bus, train, or tram line) connecting or serving the related entities.
- 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_69e2d7e509b88190a53155d4f3de45ce |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2945afa80819094f7154f7539d0d1 |
completed | April 29, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:04 a.m.