Triple
T26968410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 岸田文雄内閣 |
E679236
|
entity |
| Predicate | 政権基盤 |
P35943
|
FINISHED |
| Object | 自民党総裁岸田文雄の党内基盤 |
—
|
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: 自民党総裁岸田文雄の党内基盤 | Statement: [岸田文雄内閣, 政権基盤, 自民党総裁岸田文雄の党内基盤]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 政権基盤 Context triple: [岸田文雄内閣, 政権基盤, 自民党総裁岸田文雄の党内基盤]
-
A.
electoralBasis
Indicates the principle, rule, or criterion by which representatives or officials are chosen in an election.
-
B.
electoralBase
Indicates the group of voters or supporters that primarily backs or sustains a particular candidate, party, or political movement in elections.
-
C.
politicalFoundationFor
chosen
Indicates that one entity serves as the political basis, support, or enabling condition for the existence, authority, or functioning of another entity.
-
D.
politicalBase
Indicates the primary group, region, or constituency that provides core political support or power for an individual or organization.
-
E.
headOfGovernmentSupported
Indicates that one entity (such as a person, group, or organization) provides support—political, public, or otherwise—for the head of government of another entity.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621233f2c81908c237f20c50c2ba3 |
completed | May 2, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:37 a.m.