Triple
T34997962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porto metropolitan public transport network |
E1009591
|
entity |
| Predicate | riverBoatOperator |
P180466
|
FINISHED |
| Object | Douro river operators |
—
|
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: Douro river operators | Statement: [Porto metropolitan public transport network, riverBoatOperator, Douro river operators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverBoatOperator Context triple: [Porto metropolitan public transport network, riverBoatOperator, Douro river operators]
-
A.
shipOperator
Indicates the entity that is responsible for operating, managing, or running a ship.
-
B.
marinaOperator
Indicates that one entity operates, manages, or runs the marina facilities or services associated with another entity.
-
C.
ferryOperator
Indicates that one entity operates, manages, or runs a ferry service for another entity or in a particular context.
-
D.
riverServiceOperator
chosen
Indicates that an entity operates or manages a river-based transport or service system for another entity or area.
-
E.
boatService
Indicates that one entity provides or operates a transportation service by boat for another entity or between locations.
- 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_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:01 p.m.