Triple
T15560497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madhya Bharat |
E370983
|
entity |
| Predicate | mergedIntoOn |
P77
|
FINISHED |
| Object | Madhya Pradesh, 1956-11-01 |
—
|
LITERAL 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, 1956-11-01 | Statement: [Madhya Bharat, mergedIntoOn, Madhya Pradesh, 1956-11-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergedIntoOn Context triple: [Madhya Bharat, mergedIntoOn, Madhya Pradesh, 1956-11-01]
-
A.
mergedInto
chosen
Indicates that one entity has been combined with and absorbed into another entity, ceasing to exist as a separate unit.
-
B.
mergedBy
Indicates that one entity is combined or integrated into another entity through the action or decision of a specific agent.
-
C.
mergedOrReorganized
Indicates that one entity has combined with or been structurally reorganized into another entity, resulting in a changed or unified organizational form.
-
D.
mergedByProcess
Indicates that one or more entities are combined or unified as the result of a specific process.
-
E.
combinedIn
Indicates that two or more entities are merged, joined, or used together to form a single combined whole or context.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ddb4c0c81909b3f4c75c91f7f3f |
completed | April 16, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:09 a.m.