Triple
T19195448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 自由党 |
E469955
|
entity |
| Predicate | 合同の結果 |
P59870
|
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.
outcomeOf
chosen
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
B.
agreementOutcome
Indicates the result or consequence that follows from reaching or failing to reach an agreement between parties.
-
C.
outcomeDocument
Indicates that a particular document serves as the result, product, or formal output generated from a process, event, or action.
-
D.
contractValue
Indicates the monetary worth or agreed-upon financial amount specified in a contract between parties.
-
E.
commissionOutcome
Indicates the result or consequence produced by a commission, such as whether it was successful, failed, or led to a particular decision or action.
- 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f8a4d6b4819083fc5dd4dab05811 |
completed | April 20, 2026, 9:57 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.