Triple
T30980959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiburon as a railroad terminus |
E789369
|
entity |
| Predicate | bayTerminalType |
P170875
|
FINISHED |
| Object | rail-to-ferry transfer terminal |
—
|
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: rail-to-ferry transfer terminal | Statement: [Tiburon as a railroad terminus, bayTerminalType, rail-to-ferry transfer terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bayTerminalType Context triple: [Tiburon as a railroad terminus, bayTerminalType, rail-to-ferry transfer terminal]
-
A.
passengerTerminalType
Indicates the specific kind or category of passenger terminal associated with an entity.
-
B.
westTerminalStation
Indicates that a station serves as the western terminal (end point) of a route, line, or service.
-
C.
airportStation
Indicates a location functions as an airport facility where air transport operations occur.
-
D.
terminusAAirport
Indicates that an airport serves as the terminal (end) point for a specified air route or service.
-
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. 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:55 p.m.