Triple
T26265021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of the Crown of India |
E656955
|
entity |
| Predicate | reasonAppointmentsCeased |
P11350
|
FINISHED |
| Object | Indian independence |
—
|
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: Indian independence | Statement: [Order of the Crown of India, reasonAppointmentsCeased, Indian independence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonAppointmentsCeased Context triple: [Order of the Crown of India, reasonAppointmentsCeased, Indian independence]
-
A.
reasonForAppointment
Indicates the underlying purpose or cause for which an appointment is scheduled or taking place.
-
B.
reasonForDiscontinuation
chosen
Indicates that one entity specifies the cause or justification for stopping, ending, or withdrawing another entity, process, or activity.
-
C.
noNewAppointmentsSince
Indicates that no additional appointments have been scheduled after a specified point in time.
-
D.
reasonForNotCompletion
Indicates the explanation or cause for why a task, process, or obligation was not completed.
-
E.
ceasedRegularAppealsTo
Indicates that one entity stopped making regular appeals or requests to another entity.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 26, 2026, 9:11 p.m.