Triple
T32590149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horseshoe Bay–Langdale ferry route |
E833040
|
entity |
| Predicate | arrivalPortRegion |
P1522
|
FINISHED |
| Object | Langdale, near Gibsons |
—
|
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: Langdale, near Gibsons | Statement: [Horseshoe Bay–Langdale ferry route, arrivalPortRegion, Langdale, near Gibsons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arrivalPortRegion Context triple: [Horseshoe Bay–Langdale ferry route, arrivalPortRegion, Langdale, near Gibsons]
-
A.
placeOfArrival
chosen
Indicates the location at which an entity or person arrives at the end of a journey, movement, or transfer.
-
B.
recipientRegion
Indicates the geographic region that receives or is the destination of a transfer, delivery, or directed action.
-
C.
territoryOfDestination
Indicates that a specified territory is the destination or endpoint location associated with an action, movement, or relation.
-
D.
homeportRegion
Indicates the geographic region where a vessel’s primary homeport is located.
-
E.
associatedAirportGeographicRegion
Indicates that an airport is located within or linked to a specific geographic region.
- 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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c67138e8819099aa4ded014143ba |
completed | May 3, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:05 a.m.