Triple
T34110384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supayalat |
E874821
|
entity |
| Predicate | endOfPositionReason |
P179370
|
FINISHED |
| Object | annexation of Burma by the British |
—
|
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: annexation of Burma by the British | Statement: [Supayalat, endOfPositionReason, annexation of Burma by the British]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfPositionReason Context triple: [Supayalat, endOfPositionReason, annexation of Burma by the British]
-
A.
endOfSeriesReason
Indicates the reason or cause for which a series, sequence, or run is concluded or terminated.
-
B.
endOfAwardingReason
Indicates the reason or justification for the termination or conclusion of an awarding process or decision.
-
C.
endOf
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
-
D.
finishPosition
Indicates the final rank or place an entity achieves in an ordered outcome, such as a race, competition, or sequence of results.
-
E.
functionEndReason
Indicates the reason or cause for which a function, process, or activity comes to an end or is terminated.
- F. None of above. chosen
Provenance (4 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_69f349a80d4481908527317d43f5c579 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720cc1bfc8190a16118e3af8e9316 |
completed | May 3, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71fb0172c81908f23e95ff16b0dec |
completed | May 3, 2026, 10:13 a.m. |
Created at: May 1, 2026, 1:53 a.m.