Triple
T34154592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro Vancouver public transit network |
E876098
|
entity |
| Predicate | ferryBrand |
P138542
|
FINISHED |
| Object | SeaBus |
—
|
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: SeaBus | Statement: [Metro Vancouver public transit network, ferryBrand, SeaBus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ferryBrand Context triple: [Metro Vancouver public transit network, ferryBrand, SeaBus]
-
A.
ferryNetworkBrand
chosen
Indicates the brand or commercial identity under which a ferry network operates or is marketed.
-
B.
ferryFlightCarrier
Indicates that one carrier operates a ferry (non-revenue repositioning) flight on behalf of another carrier.
-
C.
ferryOperator
Indicates that one entity operates, manages, or runs a ferry service for another entity or in a particular context.
-
D.
ferryServiceName
Indicates the specific name assigned to a ferry service operating between locations.
-
E.
hasFerryType
Indicates that an entity (such as a ferry route or service) is associated with a specific type or category of ferry.
- 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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb5ae4c8190a6c0e578edfa60ce |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.