Triple
T36512313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akutan Airport |
E899939
|
entity |
| Predicate | distanceFromAkutanVillage |
P204911
|
FINISHED |
| Object | approximately 6 miles |
—
|
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: approximately 6 miles | Statement: [Akutan Airport, distanceFromAkutanVillage, approximately 6 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromAkutanVillage Context triple: [Akutan Airport, distanceFromAkutanVillage, approximately 6 miles]
-
A.
distanceToAdak
Indicates the measured distance from a given entity or location to Adak.
-
B.
distanceFromAnchorage
Indicates the measured distance between a given location or object and Anchorage.
-
C.
approximateDistanceFromAnchorage
Indicates the estimated spatial distance between a given entity and Anchorage, rather than an exact measured value.
-
D.
distanceToKotzebueInMiles
Indicates the numerical distance, measured in miles, between a given entity’s location and Kotzebue.
-
E.
distanceToPetropavlovskKamchatsky
Indicates the spatial distance between an entity and the location of Petropavlovsk-Kamchatsky.
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:10 p.m.