Triple
T7400341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bokaro coalfield |
E170729
|
entity |
| Predicate | hasReserves |
P1642
|
FINISHED |
| Object | large coal reserves |
—
|
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: large coal reserves | Statement: [Bokaro coalfield, hasReserves, large coal reserves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReserves Context triple: [Bokaro coalfield, hasReserves, large coal reserves]
-
A.
hasReserveStatus
Indicates that an entity holds a designated reserve or backup status in relation to another entity or role.
-
B.
hasReserveFunction
Indicates that an entity serves as a backup or secondary option that can perform the same function if the primary one is unavailable or fails.
-
C.
associatedReserve
Indicates a relationship where one entity is linked to or connected with a specific reserve (such as a backup, reserve fund, or reserved resource) designated for its use or support.
-
D.
hasReserveForces
Indicates that an entity possesses additional military or security personnel kept in reserve for potential future deployment or use.
-
E.
reserves
chosen
Indicates that an entity has arranged in advance to hold or secure something for future use or access.
- 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_69c68a5f04188190ac266569c9280347 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f24f6b7c81908cb61395239d03a0 |
completed | March 27, 2026, 9:10 p.m. |
| PD | Predicate disambiguation | batch_69c6f0323b2c819098ab72c33e6d8534 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:10 p.m.