Triple
T34998007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porto metropolitan public transport network |
E1009591
|
entity |
| Predicate | airportConnectionMode |
P33519
|
FINISHED |
| Object | metro Line E |
—
|
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: metro Line E | Statement: [Porto metropolitan public transport network, airportConnectionMode, metro Line E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportConnectionMode Context triple: [Porto metropolitan public transport network, airportConnectionMode, metro Line E]
-
A.
airportAccessMode
chosen
Indicates the typical mode or method of transportation used to access or reach an airport.
-
B.
connectsWithAirport
Indicates that there is a direct transportation or operational link established between an entity and an airport.
-
C.
hasAirsideConnection
Indicates that there is a direct, secure connection between areas past security (airside) of two locations, allowing passengers to transfer without re-clearing security or immigration.
-
D.
airportTypeManaged
Indicates that an entity is responsible for managing or overseeing a particular type or category of airport.
-
E.
airportTypePresent
Indicates that a specific type or category of airport is present or exists in relation to the referenced entity.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.