Triple
T36217065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munja |
E1047726
|
entity |
| Predicate | associatedWithPresentDayState |
P38339
|
FINISHED |
| Object | Madhya Pradesh |
E18993
|
NE 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: Madhya Pradesh | Statement: [Munja, associatedWithPresentDayState, Madhya Pradesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithPresentDayState Context triple: [Munja, associatedWithPresentDayState, Madhya Pradesh]
-
A.
associatedWithStateCode
Indicates that an entity has a connection or linkage to a particular state identified by its state code.
-
B.
associatedState
Indicates that one entity is linked or connected to a particular state, condition, or status of another entity.
-
C.
appliesToPresentDayStates
chosen
Indicates that the relationship, rule, or condition is relevant to and valid for states as they exist in the present day.
-
D.
associatedWithUSStateName
Indicates a relationship where an entity is linked or connected to the name of a U.S. state.
-
E.
governingStateAssociation
Indicates a relationship where one entity serves as the governing state or authority responsible for overseeing, regulating, or administering another entity.
- F. None of above.
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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a394d309fd481908d010df333c6a214 |
completed | June 22, 2026, 2:56 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.