Triple
T36249559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aniak Airport |
E891758
|
entity |
| Predicate | servesRemoteCommunity |
P131382
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Aniak Airport, servesRemoteCommunity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesRemoteCommunity Context triple: [Aniak Airport, servesRemoteCommunity, true]
-
A.
servesNearbyCommunities
Indicates that an entity provides services or support to communities located in its surrounding area.
-
B.
servesRemoteArea
chosen
Indicates that an entity provides services or support to people or locations in geographically remote or hard-to-reach areas.
-
C.
servesCommunitiesAlong
Indicates that something provides services or support to the communities located along a particular route, corridor, or area.
-
D.
servesCommunityDescribedAs
Indicates that an entity provides services or support to a community characterized or described in a particular way.
-
E.
servesCommunityFunction
Indicates that something performs a role or provides a service that benefits or supports a community as a whole.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a00372ff0e48190b3ed91f9bae9da6c |
completed | May 10, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_6a00359c1b8481909c1e43df9f5a789a |
completed | May 10, 2026, 7:37 a.m. |
Created at: May 3, 2026, 4:09 p.m.