Triple
T29534014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Departure Bay ferry terminal |
E749285
|
entity |
| Predicate | hasCheckInFor |
P188089
|
FINISHED |
| Object | vehicles |
—
|
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: vehicles | Statement: [Departure Bay ferry terminal, hasCheckInFor, vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCheckInFor Context triple: [Departure Bay ferry terminal, hasCheckInFor, vehicles]
-
A.
hasOnlineCheckIn
Indicates that an entity offers or supports the ability to check in via an online or digital platform.
-
B.
hasCheckInLocation
Indicates that an entity performs or is associated with a check-in action at a specific location.
-
C.
hasCheckInSystem
Indicates that an entity uses or is equipped with a system for registering or recording check-ins.
-
D.
hasCheckOutTime
Indicates the specific time at which an entity is required or scheduled to check out or depart.
-
E.
hasCheckInBuilding
Indicates that an entity has performed a check-in event within a specified building.
- F. None of above. chosen
Provenance (4 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_69f0bd47abb081909bd6e6a33d770fd8 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fba28684208190921694f23e350c3b |
completed | May 6, 2026, 8:20 p.m. |
Created at: April 28, 2026, 4:56 p.m.