Triple
T3622194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orissa |
E76751
|
entity |
| Predicate | formedAsSeparateProvince |
P25361
|
FINISHED |
| Object | 1 April 1936 |
—
|
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: 1 April 1936 | Statement: [Orissa, formedAsSeparateProvince, 1 April 1936]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedAsSeparateProvince Context triple: [Orissa, formedAsSeparateProvince, 1 April 1936]
-
A.
formerProvince
Indicates that an entity was previously a province of another entity but no longer holds that administrative status.
-
B.
joinedAsProvince
chosen
Indicates that an entity became part of a larger political or administrative unit with the status of a province.
-
C.
laterProvince
Indicates that one administrative region or province succeeds another in time, coming into existence or effect after the other.
-
D.
formerProvinceMunicipality
Indicates that a municipality previously held the status of a province-level administrative unit but no longer does.
-
E.
hasSubnationalEntitySeparated
Indicates that a subnational entity has been separated or split off from its original parent jurisdiction.
- 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2bb12cc8190bd67597cf3b66a3a |
completed | March 8, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.