Triple
T24613388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagato Domain |
E609180
|
entity |
| Predicate | notableSamurai |
P156749
|
FINISHED |
| Object | Kido Takayoshi |
—
|
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: Kido Takayoshi | Statement: [Nagato Domain, notableSamurai, Kido Takayoshi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSamurai Context triple: [Nagato Domain, notableSamurai, Kido Takayoshi]
-
A.
notableDaimyo
Indicates that a person held the status of a daimyō and is recognized as particularly prominent or historically significant among daimyō.
-
B.
hasNotableShogun
Indicates that an entity is associated with a historically notable shogun, such as by rule, leadership, or significant connection.
-
C.
notableMonk
Indicates that a person is recognized as a monk of particular significance, prominence, or historical importance.
-
D.
notableJaeger
Indicates that the subject is a Jaeger (or closely related entity) that is distinguished or prominent in some notable way, such as fame, importance, or exceptional performance.
-
E.
lastShogun
Indicates that the subject is the final individual to hold the position or title of shogun in a given historical or organizational context.
- F. None of above. chosen
Provenance (4 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_69e2c4d1140081909c58667bf68f80c3 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:31 a.m.