Triple
T21685260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 寺内内閣 |
E535212
|
entity |
| Predicate | 外交上の出来事 |
P52594
|
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.
diplomaticActivity
chosen
Indicates engagement in formal or informal diplomatic actions or interactions between parties, such as negotiations, consultations, or representation.
-
B.
diplomaticPost
Indicates that an entity holds or is assigned to an official diplomatic position or mission representing one state or organization to another.
-
C.
diplomaticArena
Indicates a context or setting in which diplomatic interactions, negotiations, or relations between entities take place.
-
D.
diplomaticSignificance
Indicates the importance or impact that an event, action, or entity has within diplomatic relations between parties or states.
-
E.
politicalEvent
Indicates an occurrence related to political processes, activities, or changes involving governance, power, or public policy.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96ca668481909f53853c7a8ea811 |
completed | April 27, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:44 p.m.