Triple
T38085991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eiroku 3 |
E950977
|
entity |
| Predicate | associatedDaimyo |
P160260
|
FINISHED |
| Object | Oda Nobunaga |
E164137
|
NE 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: Oda Nobunaga | Statement: [Eiroku 3, associatedDaimyo, Oda Nobunaga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDaimyo Context triple: [Eiroku 3, associatedDaimyo, Oda Nobunaga]
-
A.
notableDaimyo
Indicates that a person held the status of a daimyō and is recognized as particularly prominent or historically significant among daimyō.
-
B.
lastDaimyo
Indicates that the subject is the final or most recent daimyo (feudal lord) to hold authority over the object.
-
C.
daimyoStatus
chosen
Indicates that one entity holds the status or role of a daimyo in relation to another entity or context.
-
D.
firstDaimyo
Indicates that the subject is the first (initial or founding) daimyō associated with the specified domain, lineage, or context.
-
E.
daimyōFamily
Indicates a familial relationship involving a daimyō, such as belonging to or being part of a daimyō’s family.
- F. None of above.
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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41680a4bf88190ad7d99e9afa2b668 |
completed | June 28, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.