Triple
T12447116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Tmetuchl International Airport |
E297429
|
entity |
| Predicate | distanceToKororKilometers |
P105064
|
FINISHED |
| Object | approximately 6 |
—
|
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 | Statement: [Roman Tmetuchl International Airport, distanceToKororKilometers, approximately 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToKororKilometers Context triple: [Roman Tmetuchl International Airport, distanceToKororKilometers, approximately 6]
-
A.
distanceToPalikir
Indicates the spatial distance between a given location and Palikir.
-
B.
distanceFromRarotonga
Indicates the spatial distance between a given entity and the location of Rarotonga.
-
C.
distanceToForster_km
Indicates the physical distance, measured in kilometers, between an entity and a reference location named Forster.
-
D.
distanceFromKaunakakaiMiles
Indicates the physical distance, measured in miles, between an entity and the location of Kaunakakai.
-
E.
distanceToDiliBySea
Indicates the measured or estimated distance between an entity and Dili when traveling via sea routes.
- 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_69d6ada166c48190b902972cd2408fa3 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95151e7348190a1d4953a8b416a13 |
completed | April 10, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69d94d3c27a08190a0237200203e476d |
completed | April 10, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69d9511989ac8190ade98f52f66f7cd4 |
completed | April 10, 2026, 7:35 p.m. |
Created at: April 8, 2026, 9:56 p.m.