Triple
T36053811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chōsokabe clan |
E1042888
|
entity |
| Predicate | lostControlOfShikokuTo |
P76678
|
FINISHED |
| Object | Toyotomi Hideyoshi |
—
|
NE NERFINISHED |
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: Toyotomi Hideyoshi | Statement: [Chōsokabe clan, lostControlOfShikokuTo, Toyotomi Hideyoshi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostControlOfShikokuTo Context triple: [Chōsokabe clan, lostControlOfShikokuTo, Toyotomi Hideyoshi]
-
A.
wasUnderJapaneseControlUntil
Indicates that an entity was governed, occupied, or administered by Japan up to a specified end date or time period.
-
B.
governingShogunate
Indicates that a particular shogunate holds governing authority or political control over a specified entity or region.
-
C.
lostSovereignty
chosen
Indicates that an entity has ceased to possess independent authority or control over its own governance or territory.
-
D.
lostSovereigntyIn
Indicates that an entity ceased to possess or exercise sovereign authority within a specified place or domain.
-
E.
terminusOnHonshu
Indicates that the endpoint or terminus of something (such as a route, line, or connection) is located on the island of Honshu.
- 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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.