Triple
T15715368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berhampur |
E380945
|
entity |
| Predicate | distanceToGopalpurOnSea |
P119893
|
FINISHED |
| Object | approximately 15 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 15 km | Statement: [Berhampur, distanceToGopalpurOnSea, approximately 15 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToGopalpurOnSea Context triple: [Berhampur, distanceToGopalpurOnSea, approximately 15 km]
-
A.
distanceToParikia
Indicates the spatial distance between a given location or object and Parikia.
-
B.
distanceFromPortBlair
Indicates the measured distance between a given location and Port Blair.
-
C.
distanceToSomnath
Indicates the spatial distance between a given entity or location and Somnath.
-
D.
distanceToSantiniketanKmApprox
Indicates an approximate distance, measured in kilometers, from a given entity to Santiniketan.
-
E.
approxDistanceInKilometersFromWandoorJetty
Indicates an approximate distance, measured in kilometers, between a subject entity and the Wandoor Jetty location.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f91beb08190bd91bf9306737c3b |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e0094af5b481908ad51d5d7ba0c726 |
completed | April 15, 2026, 9:55 p.m. |
Created at: April 10, 2026, 4:45 a.m.