Triple
T29105034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Point Defiance–Tahlequah ferry route |
E736738
|
entity |
| Predicate | endpointLocation |
P390
|
FINISHED |
| Object | southern tip of Vashon Island |
—
|
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: southern tip of Vashon Island | Statement: [Point Defiance–Tahlequah ferry route, endpointLocation, southern tip of Vashon Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endpointLocation Context triple: [Point Defiance–Tahlequah ferry route, endpointLocation, southern tip of Vashon Island]
-
A.
endPoint
chosen
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
B.
connectionLocation
Indicates the place or spatial context where a connection between entities occurs or is established.
-
C.
operationLocation
Indicates the place or site where an operation, activity, or process is carried out.
-
D.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
-
E.
serviceLocation
Indicates the place or address where a service is provided, performed, or made available to the relevant party.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 11:15 a.m.