Triple
T35048060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porto Metro at Aliados station |
E1011255
|
entity |
| Predicate | isCentralStopOn |
P15947
|
FINISHED |
| Object | Porto Metro Line D |
—
|
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: Porto Metro Line D | Statement: [Porto Metro at Aliados station, isCentralStopOn, Porto Metro Line D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCentralStopOn Context triple: [Porto Metro at Aliados station, isCentralStopOn, Porto Metro Line D]
-
A.
hasCentralTerminus
Indicates that one entity serves as the primary or central terminus (end point or hub) for another entity.
-
B.
isCityCentreStop
chosen
Indicates that a stop is located within or serves the central area of a city.
-
C.
isCentralTo
Indicates that something plays a primary, essential, or defining role in relation to something else, such that the latter depends on or is organized around it.
-
D.
isPassengerStop
Indicates that a location serves as a designated place where passengers may board or alight from a vehicle or transport service.
-
E.
isPopularStopFor
Indicates that a location is frequently visited or favored as a stop or destination by a particular group or type of traveler.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:01 p.m.