Triple
T25082313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vyner Brooke |
E628217
|
entity |
| Predicate | reasonForCession |
P88040
|
FINISHED |
| Object | post-World War II political and financial pressures |
—
|
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: post-World War II political and financial pressures | Statement: [Vyner Brooke, reasonForCession, post-World War II political and financial pressures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForCession Context triple: [Vyner Brooke, reasonForCession, post-World War II political and financial pressures]
-
A.
reasonForRetrocession
Indicates the underlying cause or justification for a retrocession event or decision.
-
B.
requiredCessionTo
Indicates that one entity must transfer or yield rights, control, or ownership to another entity as a necessary condition.
-
C.
reasonForSale
Indicates the underlying cause, motivation, or circumstance that explains why something is being sold.
-
D.
transferReason
chosen
Indicates the reason or justification for a transfer occurring between entities.
-
E.
reasonForSettlement
Indicates the underlying cause, motivation, or circumstance that led to a settlement being made.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 18, 2026, 6:22 a.m.