Triple
T8856375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orzola |
E210766
|
entity |
| Predicate | mainDeparturePointFor |
P1521
|
FINISHED |
| Object | ferries to La Graciosa |
—
|
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: ferries to La Graciosa | Statement: [Orzola, mainDeparturePointFor, ferries to La Graciosa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainDeparturePointFor Context triple: [Orzola, mainDeparturePointFor, ferries to La Graciosa]
-
A.
departsFrom
Indicates that an entity (such as a vehicle, person, or process) begins its movement, journey, or operation starting from a specified location or point of origin.
-
B.
placeOfDeparture
chosen
Indicates the location from which an entity, such as a person or vehicle, begins its journey or movement.
-
C.
isMainBusStationFor
Indicates that one bus station serves as the primary or central station for a particular area, network, or service.
-
D.
commuterDestination
Indicates that a location serves as the endpoint or target place to which a person regularly travels for commuting.
-
E.
startingStation
Indicates the station or location where a journey, route, or trip begins.
- 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_69ca838a424c8190b1ecac115c2927e7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60e259248190abd334bbfcdcb955 |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:50 p.m.