Triple
T36102630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kobayakawa Takakage |
E1044254
|
entity |
| Predicate | successorClanHead |
P76270
|
FINISHED |
| Object | Kobayakawa Hideaki |
—
|
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: Kobayakawa Hideaki | Statement: [Kobayakawa Takakage, successorClanHead, Kobayakawa Hideaki]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorClanHead Context triple: [Kobayakawa Takakage, successorClanHead, Kobayakawa Hideaki]
-
A.
successorClan
Indicates that one clan directly follows and replaces another clan in a sequence or lineage.
-
B.
laterHeadOfClan
Indicates that the subject entity becomes the head of the clan at a later time than the object entity.
-
C.
predecessorAsHeadOfClan
chosen
Indicates that one entity previously held the position of head of the clan immediately before the other entity.
-
D.
successorAsDaijoDaijin
Indicates that one individual succeeded another in holding the position of Daijō-daijin (Chancellor of the Realm) in the Japanese imperial government.
-
E.
successorAsChief
Indicates that one entity becomes the next chief, taking over the leadership role from another entity.
- 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_69f76e338e2c8190b7f3bc68bec76349 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a004d0b46148190bcec4ea67acfe170 |
completed | May 10, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_6a004c92283081909f229c1720af155a |
completed | May 10, 2026, 9:14 a.m. |
Created at: May 3, 2026, 4:08 p.m.