Triple
T36687564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krishna I |
E905861
|
entity |
| Predicate | ruledPartOfPresentDayState |
P79970
|
FINISHED |
| Object | Maharashtra |
—
|
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: Maharashtra | Statement: [Krishna I, ruledPartOfPresentDayState, Maharashtra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruledPartOfPresentDayState Context triple: [Krishna I, ruledPartOfPresentDayState, Maharashtra]
-
A.
locatedInModernState
Indicates that one entity is geographically situated within the boundaries of a specified contemporary nation-state.
-
B.
governingStateInHistory
Indicates that one state historically exercised governing authority or control over another entity during a specific period in the past.
-
C.
becamePartOfState
Indicates that an entity transitioned from a different status or jurisdiction to become incorporated into a particular state.
-
D.
stateRuled
chosen
Indicates that a particular state is governed or controlled by a specified ruler or ruling entity.
-
E.
partOfModernStateSince
Indicates that one entity has been incorporated into and belongs to the territory or jurisdiction of a specified modern state starting from a given point in time.
- 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.