Triple
T18013427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokugawa clan |
E430939
|
entity |
| Predicate | governmentTypeExercised |
P220
|
FINISHED |
| Object | bakufu |
—
|
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: bakufu | Statement: [Tokugawa clan, governmentTypeExercised, bakufu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentTypeExercised Context triple: [Tokugawa clan, governmentTypeExercised, bakufu]
-
A.
governmentTypeDuringUse
Indicates the form of government that was in place while something (such as a building, site, or object) was in use.
-
B.
governmentType
chosen
Indicates the form or system of governance under which an entity (such as a country or organization) is organized and ruled.
-
C.
governmentTypeServed
Indicates the type of government that an entity serves, is affiliated with, or operates under in its role or function.
-
D.
governmentTypeAffected
Indicates that an action, event, or condition has an impact on the form, structure, or functioning of a government type.
-
E.
governmentTypeReflected
Indicates that the government type of one entity is represented, mirrored, or exemplified by another entity.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b521befc81908dff44f19aa3d580 |
completed | April 19, 2026, 10:57 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:24 a.m.