Triple
T35479368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tozama domain |
E1025426
|
entity |
| Predicate | hasRelationshipToShogunate |
P207003
|
FINISHED |
| Object | distant |
—
|
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: distant | Statement: [tozama domain, hasRelationshipToShogunate, distant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelationshipToShogunate Context triple: [tozama domain, hasRelationshipToShogunate, distant]
-
A.
statusOfShogunate
Indicates the political or operational condition or state of a shogunate at a given time.
-
B.
governingShogunate
Indicates that a particular shogunate holds governing authority or political control over a specified entity or region.
-
C.
relationshipToToyotomiHideyoshi
Indicates the nature of a person or entity’s relationship or association to Toyotomi Hideyoshi.
-
D.
hasNotableShogun
Indicates that an entity is associated with a historically notable shogun, such as by rule, leadership, or significant connection.
-
E.
usedUnderShogun
Indicates that something was utilized or operated under the authority, control, or governance of a shogun.
- 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_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:04 p.m.