Triple
T37879767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ōnin |
E944837
|
entity |
| Predicate | associatedWithFeudalLords |
P122865
|
FINISHED |
| Object | daimyō |
—
|
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: daimyō | Statement: [Ōnin, associatedWithFeudalLords, daimyō]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFeudalLords Context triple: [Ōnin, associatedWithFeudalLords, daimyō]
-
A.
associatedWithFeudalSystem
Indicates a relationship in which something is connected, linked, or relevant to the structures, practices, or institutions of a feudal system.
-
B.
associatedWithFeudalOffice
chosen
Indicates a relationship where an entity is linked to, holds, or is otherwise connected with a specific feudal office or position within a feudal system.
-
C.
feud
Indicates a prolonged, mutual state of hostility or conflict between two or more parties.
-
D.
laterFeudalStatus
Indicates that one entity held a particular feudal status or rank at a later time than another entity or than an earlier status.
-
E.
hasFeudalOverlord
Indicates that one entity holds feudal lordship or overlord authority over another, implying hierarchical control and obligations within a feudal system.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.