Triple
T27114983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnpur |
E686816
|
entity |
| Predicate | abbreviationOfMajorPlant |
P161866
|
FINISHED |
| Object | IISCO Steel Plant |
—
|
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: IISCO Steel Plant | Statement: [Burnpur, abbreviationOfMajorPlant, IISCO Steel Plant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abbreviationOfMajorPlant Context triple: [Burnpur, abbreviationOfMajorPlant, IISCO Steel Plant]
-
A.
botanicalAuthorAbbreviation
Indicates the standardized abbreviated form of a botanist’s name used to cite them as the author of a plant’s scientific name.
-
B.
operatorOfMajorPlant
Indicates that an entity operates or manages a major industrial or production plant.
-
C.
famousPlants
Indicates that the plants in question are widely known or celebrated, typically for their distinctive characteristics, history, or cultural significance.
-
D.
scientificNameAbbreviation
Indicates that one entity is an abbreviated or shortened form of the scientific name of another entity.
-
E.
standardFormInBotany
Indicates that something is expressed or recorded using the conventional, officially accepted format used in botanical nomenclature or documentation.
- 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_69ef148c2b588190afc15b529f7af845 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f624059f7c8190b245dc53535a1ff2 |
completed | May 2, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fa35ac48190890102c348ed81a0 |
completed | May 2, 2026, 4 p.m. |
Created at: April 27, 2026, 8:56 a.m.