Triple
T27274237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kwethluk, Alaska |
E688139
|
entity |
| Predicate | transportationReliantOn |
P87132
|
FINISHED |
| Object | small aircraft |
—
|
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: small aircraft | Statement: [Kwethluk, Alaska, transportationReliantOn, small aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportationReliantOn Context triple: [Kwethluk, Alaska, transportationReliantOn, small aircraft]
-
A.
transportationReliance
chosen
Indicates the extent to which one entity depends on another entity or mode for its transportation needs.
-
B.
usedTransportationInfrastructure
Indicates that an entity made use of some form of transportation infrastructure (such as roads, railways, or ports) to enable movement or transit.
-
C.
transportationNeed
Indicates that an entity requires or lacks adequate means of transportation to reach a destination or perform an activity.
-
D.
hasTransportationSystem
Indicates that an entity possesses, operates, or is served by an organized system for transporting people or goods.
-
E.
usedTransportationMode
Indicates that an entity traveled or moved using a specified mode of transportation.
- 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 27, 2026, 11:01 a.m.