Triple
T27706097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UP |
E698562
|
entity |
| Predicate | periodAsOfficialOpposition |
P81041
|
FINISHED |
| Object | 1948–1977 |
—
|
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: 1948–1977 | Statement: [UP, periodAsOfficialOpposition, 1948–1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodAsOfficialOpposition Context triple: [UP, periodAsOfficialOpposition, 1948–1977]
-
A.
termEndAsLeaderOfOpposition
Indicates the point in time when an entity’s tenure serving as leader of the opposition comes to an end.
-
B.
succeededByAsLeaderOfOpposition
Indicates that one person directly followed another as the official leader of the opposition.
-
C.
officialOppositionPeriodEnd
chosen
Indicates the point in time when an entity’s role or status as the official opposition comes to an end.
-
D.
electoralRoleWhenInOpposition
Indicates the specific political or parliamentary role an individual holds while their party or group is in opposition rather than in government.
-
E.
wasOppositionStrongholdDuring
Indicates that a particular place served as a primary base or strong area of support for an opposition group during a specified time period.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 2:59 p.m.