Triple
T6211908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shahdol |
E138889
|
entity |
| Predicate | locatedInRegionRichIn |
P9687
|
FINISHED |
| Object | coal |
—
|
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: coal | Statement: [Shahdol, locatedInRegionRichIn, coal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInRegionRichIn Context triple: [Shahdol, locatedInRegionRichIn, coal]
-
A.
foundInRegion
chosen
Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial region.
-
B.
locatedInAgriculturalRegion
Indicates that an entity is situated within a region primarily characterized by agricultural activities or land use.
-
C.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
D.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
E.
locatedInCountyRegion
Indicates that one entity is geographically situated within the boundaries of a specific county or county-level region.
- 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_69c008ada364819096c9e92c74d639b5 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0628adccc8190b94f5c2c1d5d03f7 |
completed | March 22, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c055fdea3c81908f5d910f0d36234a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:21 p.m.