Triple
T35479375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tozama domain |
E1025426
|
entity |
| Predicate | hasRulerStatus |
P184052
|
FINISHED |
| Object | non-hereditary Tokugawa vassal before Sekigahara |
—
|
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: non-hereditary Tokugawa vassal before Sekigahara | Statement: [tozama domain, hasRulerStatus, non-hereditary Tokugawa vassal before Sekigahara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRulerStatus Context triple: [tozama domain, hasRulerStatus, non-hereditary Tokugawa vassal before Sekigahara]
-
A.
hasRulerCharacter
Indicates that a ruler possesses a particular character trait or quality.
-
B.
hasRulerTitle
Indicates that a ruler holds or is associated with a specific formal title of rulership.
-
C.
hasTypeOfRuler
Indicates that one entity serves as the specific kind or category of ruler (e.g., monarch, dictator, president) that characterizes or governs another entity.
-
D.
hasSignificantRuler
Indicates that an entity has or had a ruler whose leadership is considered historically or contextually important.
-
E.
hasRulerNamingCustom
Indicates that a political entity follows a particular custom or convention for naming its ruler.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:04 p.m.