Triple
T34997960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porto metropolitan public transport network |
E1009591
|
entity |
| Predicate | funicularOperator |
P33423
|
FINISHED |
| Object | Metro do Porto |
—
|
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 do Porto | Statement: [Porto metropolitan public transport network, funicularOperator, Metro do Porto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: funicularOperator Context triple: [Porto metropolitan public transport network, funicularOperator, Metro do Porto]
-
A.
cableCarOperator
chosen
Indicates that one entity operates, manages, or runs a cable car service for another entity or location.
-
B.
funicularRailwayName
Indicates that a funicular railway has the specified name.
-
C.
hasFunicular
Indicates that one place or facility is equipped with or served by a funicular railway connection to another location.
-
D.
funicularOpeningDate
Indicates the calendar date on which a funicular railway was first opened for operation.
-
E.
tramOperator
Indicates that one entity operates, manages, or runs tram services for another entity or area.
- 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.