Triple
T28086087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jindal Vijayanagar Steel Ltd. |
E709824
|
entity |
| Predicate | hasMajorPlantLocation |
P43763
|
FINISHED |
| Object | Toranagallu, Karnataka |
—
|
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: Toranagallu, Karnataka | Statement: [Jindal Vijayanagar Steel Ltd., hasMajorPlantLocation, Toranagallu, Karnataka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorPlantLocation Context triple: [Jindal Vijayanagar Steel Ltd., hasMajorPlantLocation, Toranagallu, Karnataka]
-
A.
hasMajorPlant
chosen
Indicates that one entity possesses or hosts a primary or most significant plant facility or installation in relation to another entity.
-
B.
hasMajorLocation
Indicates that an entity is primarily situated in, based in, or most significantly associated with a particular location.
-
C.
plantLocation
Indicates the location where a plant is situated, grown, or found.
-
D.
isMajorPlant
Indicates that a plant holds primary or dominant importance within a given context, such as size, influence, or role.
-
E.
pressingPlantLocation
Indicates the location where a plant is being or has been pressed (e.g., for preservation or processing).
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
Created at: April 27, 2026, 8:55 p.m.