Triple
T10063611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munnar |
E213045
|
entity |
| Predicate | distanceToKochi |
P59299
|
FINISHED |
| Object | about 130 kilometres |
—
|
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: about 130 kilometres | Statement: [Munnar, distanceToKochi, about 130 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToKochi Context triple: [Munnar, distanceToKochi, about 130 kilometres]
-
A.
distanceFromKochi_km
chosen
Indicates the physical distance, measured in kilometers, between a given location and Kochi.
-
B.
distanceToKyushu
Indicates the spatial distance between a given entity’s location and the region of Kyushu.
-
C.
distanceToSapporo
Indicates the measured or calculated distance between a given entity and the location of Sapporo.
-
D.
distanceFromOsaka
Indicates the measured distance between a given place or object and the city of Osaka.
-
E.
distanceFromKyoto
Indicates the measured spatial distance between a given entity’s location and the city of Kyoto.
- 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_69ca83977128819084084eb7d1d8c52a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdcfd4e4ac8190a37061b4082caa48 |
completed | April 2, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:58 p.m.