Triple
T27488197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 広田弘毅 |
E693800
|
entity |
| Predicate | 関与した条約・協定 |
P5763
|
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.
relatedToTreaty
chosen
Indicates that there exists a connection, association, or relevance between an entity and a specific treaty or treaties.
-
B.
linkedToTreaty
Indicates that an entity has a formal connection or association with a specific treaty, such as being established by, governed by, or otherwise related to that treaty.
-
C.
treatyMention
Indicates that a treaty is referenced or mentioned in relation to the associated entities or context.
-
D.
linkedTreaty
Indicates that there is a formal treaty connection or association between the related entities, such as being parties to, or otherwise bound by, the same treaty.
-
E.
resultOfTreaties
Indicates that something exists, occurs, or holds true as a consequence or outcome of one or more treaties.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62e86625081909d5cc4b5fc1bd3d5 |
completed | May 2, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:03 p.m.