Triple
T29611500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhilai Steel Plant |
E754735
|
entity |
| Predicate | formerLocationState |
P197322
|
FINISHED |
| Object | Madhya Pradesh |
—
|
NE NERFINISHED |
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: Madhya Pradesh | Statement: [Bhilai Steel Plant, formerLocationState, Madhya Pradesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerLocationState Context triple: [Bhilai Steel Plant, formerLocationState, Madhya Pradesh]
-
A.
formerState
Indicates that an entity previously held the status or condition of a particular state but no longer does so.
-
B.
originalLocationStatus
Indicates the status or condition of an entity’s original location, such as whether it remains, has changed, or is otherwise affected.
-
C.
previousLocationName
Indicates that one entity specifies the name of a location where another entity was situated or occurred before its current location.
-
D.
formerlyKnownLocationAs
Indicates that an entity was previously known or referred to by a different location name or designation.
-
E.
formerlyLocatedOn
Indicates that an entity was once located on or situated upon another entity, but is no longer in that position.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
| PDg | Predicate description generation | batch_69fe87b52bd4819087d6d338fe47c97c |
completed | May 9, 2026, 1:02 a.m. |
Created at: April 28, 2026, 6:28 p.m.