Triple
T10233586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor of Hindustan |
E243403
|
entity |
| Predicate | endedWithAction |
P3587
|
FINISHED |
| Object | exile of Bahadur Shah II to Rangoon |
—
|
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: exile of Bahadur Shah II to Rangoon | Statement: [Emperor of Hindustan, endedWithAction, exile of Bahadur Shah II to Rangoon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endedWithAction Context triple: [Emperor of Hindustan, endedWithAction, exile of Bahadur Shah II to Rangoon]
-
A.
endedWith
chosen
Indicates that one event, process, or state concluded with or was finalized by another specified event, condition, or outcome.
-
B.
concludedWith
Indicates that an event, process, or interaction ended or was finalized by a specific outcome, action, or state.
-
C.
endedFunctionallyWith
Indicates that a process, event, or relationship has effectively concluded in practice, even if it has not been formally or officially terminated.
-
D.
attemptedAction
Indicates that an entity made an effort to perform a particular action, regardless of whether the action was successfully completed.
-
E.
subsequentAction
Indicates that one action occurs after another in time, following it as a later step or consequence.
- 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_69d381b0f97c819085c9b45799a5fb7c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d23b620c8190b8a72d0eb0d16b93 |
completed | April 7, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69d4d1e9798c8190b437d53d48554ba1 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:21 a.m.