Triple
T2212174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kona International Airport |
E50941
|
entity |
| Predicate | distanceFromKailuaKonaMiles |
P36818
|
FINISHED |
| Object | approximately 7 |
—
|
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 7 | Statement: [Kona International Airport, distanceFromKailuaKonaMiles, approximately 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromKailuaKonaMiles Context triple: [Kona International Airport, distanceFromKailuaKonaMiles, approximately 7]
-
A.
distanceToHelsinki_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Helsinki.
-
B.
distanceToCancun
Indicates the measured or calculated spatial distance between a given entity and the location of Cancun.
-
C.
distanceToSeattle
Indicates the measured or calculated distance between a given entity’s location and the city of Seattle.
-
D.
range_km
Indicates the maximum distance, measured in kilometers, over which something can operate, travel, or be effective.
-
E.
approximateLengthInMiles
Indicates the estimated distance or extent of something measured in miles.
- 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_69a88b06709c8190978fb2418470d1b6 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfecea6c8190b762bbfda8490e31 |
completed | March 7, 2026, 6:04 a.m. |
| PD | Predicate disambiguation | batch_69abbdaa26d48190860c33fd464c4845 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbf0c2b8881908553eed5be17a9c2 |
completed | March 7, 2026, 6 a.m. |
Created at: March 4, 2026, 7:46 p.m.