Triple
T2197858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trimbakeshwar |
E50416
|
entity |
| Predicate | distanceFromNashik |
P36893
|
FINISHED |
| Object | Approximately 28 km |
—
|
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 28 km | Statement: [Trimbakeshwar, distanceFromNashik, Approximately 28 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromNashik Context triple: [Trimbakeshwar, distanceFromNashik, Approximately 28 km]
-
A.
distanceToNagpur
Indicates the spatial distance between a given entity’s location and the city of Nagpur.
-
B.
distanceFromJaipur
Indicates the spatial distance between a given entity and the location Jaipur.
-
C.
distanceToWardha
Indicates the spatial distance between a given entity and the location named Wardha.
-
D.
distanceToDelhiByRoad_km
Indicates the road travel distance, measured in kilometers, from a given place to Delhi.
-
E.
distanceFromMathura
Indicates the spatial distance between a given entity or location and the city of Mathura.
- 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbf79f3e08190b56e9d7c0ff27237 |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbda706f4819094de73e1d1d1f539 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbf35c994819088a093c412931de4 |
completed | March 7, 2026, 6:01 a.m. |
Created at: March 4, 2026, 7:46 p.m.