Triple
T13441433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yakutat Airport |
E320369
|
entity |
| Predicate | isLocatedOnCoast |
P11059
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Yakutat Airport, isLocatedOnCoast, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedOnCoast Context triple: [Yakutat Airport, isLocatedOnCoast, yes]
-
A.
locatedOnCoastAt
Indicates that one entity is situated on the coastline at the specific location represented by another entity.
-
B.
isPartOfCoastOf
Indicates that one entity forms a segment or component of the coastline belonging to another entity.
-
C.
basedOnCoast
chosen
Indicates that something is situated along, adjacent to, or directly influenced by a coastline.
-
D.
hasCoastlineOn
Indicates that one entity’s coastline borders or is directly adjacent to a specified body of water.
-
E.
hasCoastline
Indicates that a geographic entity is bordered by and directly touches a sea or ocean along part of its boundary.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaee704ac8190b4c7f4e0d3a88494 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.