Triple
T24288209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sei-i Taishōgun |
E605732
|
entity |
| Predicate | inceptionAsFeudalOffice |
P122865
|
FINISHED |
| Object | 1192 |
—
|
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: 1192 | Statement: [Sei-i Taishōgun, inceptionAsFeudalOffice, 1192]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inceptionAsFeudalOffice Context triple: [Sei-i Taishōgun, inceptionAsFeudalOffice, 1192]
-
A.
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.
-
B.
feudalFunction
Indicates the role or duty an entity holds within a feudal hierarchy, such as obligations, services, or functions owed to or performed for another.
-
C.
definesOfficeOf
Indicates that one entity specifies or establishes the official role, position, or office associated with another entity.
-
D.
natureOfOffice
Indicates the type or character of an office or position, specifying what kind of role or function it represents.
-
E.
isHistoricOffice
Indicates that an office or position has historical significance, typically due to its age, legacy, or role in past events.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f57a9a08190b183879ff76071d0 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:08 a.m.