Triple
T18836841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khatia |
E460685
|
entity |
| Predicate | isEntryPointFor |
P26093
|
FINISHED |
| Object | jeep safaris into Kanha National Park |
—
|
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: jeep safaris into Kanha National Park | Statement: [Khatia, isEntryPointFor, jeep safaris into Kanha National Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEntryPointFor Context triple: [Khatia, isEntryPointFor, jeep safaris into Kanha National Park]
-
A.
entryPointFor
chosen
Indicates that one entity serves as the access or starting location through which another entity is entered, initiated, or reached.
-
B.
isRouteFor
Indicates that one entity serves as a path, course, or channel used for traveling, transporting, or connecting to another entity.
-
C.
isDestinationFor
Indicates that one entity serves as the endpoint or target location that another entity is intended to reach or be directed toward.
-
D.
isRouteOn
Indicates that one route is located on, follows along, or is aligned with another specified path or infrastructure.
-
E.
isServedFor
Indicates that something is provided or presented as suitable or intended for a particular purpose, use, or recipient.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a99e86388190957acaaab401b5cb |
completed | April 20, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.