Triple
T34292215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chatra district |
E879920
|
entity |
| Predicate | locatedInPlateau |
P94996
|
FINISHED |
| Object | Chota Nagpur Plateau |
E166604
|
NE 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: Chota Nagpur Plateau | Statement: [Chatra district, locatedInPlateau, Chota Nagpur Plateau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInPlateau Context triple: [Chatra district, locatedInPlateau, Chota Nagpur Plateau]
-
A.
locatedOnPlateauBetween
Indicates that one entity is situated on a plateau that lies between two other referenced geographic or spatial entities.
-
B.
isOnHighPlains
chosen
Indicates that something is located on or situated within a region of elevated, relatively flat high plains.
-
C.
hasNearbyPlateau
Indicates that one geographic entity is located close to or adjacent to a plateau.
-
D.
locatedOnPeak
Indicates that one entity is situated at or on the summit or highest point of another entity (a peak).
-
E.
isLocatedInCentralPlainOf
Indicates that one entity is situated within the central plain region of another entity’s geographic area.
- F. None of above.
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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37181a265c8190b26470f607405593 |
completed | June 20, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:57 a.m.