Triple
T14058165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adanwomase |
E338271
|
entity |
| Predicate | distanceFromKumasi |
P112660
|
FINISHED |
| Object | approximately 27 kilometers |
—
|
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 27 kilometers | Statement: [Adanwomase, distanceFromKumasi, approximately 27 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromKumasi Context triple: [Adanwomase, distanceFromKumasi, approximately 27 kilometers]
-
A.
distanceToKyushu
Indicates the spatial distance between a given entity’s location and the region of Kyushu.
-
B.
distanceFromKochi_km
Indicates the physical distance, measured in kilometers, between a given location and Kochi.
-
C.
distanceFromKyoto
Indicates the measured spatial distance between a given entity’s location and the city of Kyoto.
-
D.
distanceFromKyotoStation
Indicates the spatial distance between a given location and Kyoto Station.
-
E.
distanceFromKuching
Indicates the spatial distance between a given location and Kuching.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de3c8e6d008190af8892f34c5cefbd |
completed | April 14, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:20 p.m.