Triple
T515661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japan Socialist Party |
E10700
|
entity |
| Predicate | oppositionPeriodStart |
P15443
|
FINISHED |
| Object | 1955 |
—
|
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: 1955 | Statement: [Japan Socialist Party, oppositionPeriodStart, 1955]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oppositionPeriodStart Context triple: [Japan Socialist Party, oppositionPeriodStart, 1955]
-
A.
electoralAlliancePeriod
Indicates the time span during which two or more political entities are formally joined in an electoral alliance.
-
B.
startTimeAsRulingParty
Indicates the point in time when an entity begins its tenure or role as the ruling party.
-
C.
legislativePeriod
Indicates the specific legislative term or session during which an action, event, or status is valid or took place.
-
D.
parliamentaryOppositionTo
Indicates that one party, group, or member within a parliamentary system formally opposes the policies, actions, or proposals of another.
-
E.
opponentCandidate
Indicates that one entity is a rival or competing candidate against another in the same contest or election.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f232fa688190b08a2fe3f22c7a6e |
completed | Feb. 28, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69a2f013c05481909e6dc87e7b20ebd8 |
completed | Feb. 28, 2026, 1:39 p.m. |
| PDg | Predicate description generation | batch_69a2f23214248190aa5fe1138f0f5a58 |
completed | Feb. 28, 2026, 1:48 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.