Triple
T8083145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yasuko Hatoyama |
E188665
|
entity |
| Predicate | usedWealthFor |
P43040
|
FINISHED |
| Object | funding Yukio Hatoyama’s political activities |
—
|
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: funding Yukio Hatoyama’s political activities | Statement: [Yasuko Hatoyama, usedWealthFor, funding Yukio Hatoyama’s political activities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedWealthFor Context triple: [Yasuko Hatoyama, usedWealthFor, funding Yukio Hatoyama’s political activities]
-
A.
incomeUsedFor
Indicates that some or all of an income amount is allocated or spent for a specified purpose, activity, or recipient.
-
B.
usedCapital
Indicates that an entity made use of a particular capital city as its seat of government or primary administrative center.
-
C.
usedFund
chosen
Indicates that one entity expended or applied a particular fund or financial resource for some purpose.
-
D.
hasWealthSource
Indicates that an entity derives its wealth or financial resources from a specified source.
-
E.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
- 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_69ca82b662e88190b9323daab8c28a21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb415cb4688190920868317e77bbff |
completed | March 31, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69cb049f1614819087360d1a4c6f0faa |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:28 p.m.