Triple
T35467258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yanagisawa clan |
E1025109
|
entity |
| Predicate | servedGovernment |
P53045
|
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: [Yanagisawa clan, servedGovernment, bakufu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedGovernment Context triple: [Yanagisawa clan, servedGovernment, bakufu]
-
A.
servedInGovernmentWith
Indicates that two individuals held positions in the same government or administration during an overlapping period of time.
-
B.
governmentServed
Indicates that a person has held a position serving in or working for a particular government.
-
C.
governmentBodyServed
chosen
Indicates that one entity has served in an official capacity within, or as a member of, a particular government body.
-
D.
hasGovernmentServicesProvidedBy
Indicates that one entity receives its governmental services from, or is administratively served by, another entity.
-
E.
servesLevelOfGovernment
Indicates that one entity performs duties or functions on behalf of, or under the authority of, a specified level of government (e.g., local, regional, national).
- 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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a000be59ad88190a6aa3a42c097796d |
completed | May 10, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_6a000ab6e9bc81908300b81d004e5921 |
completed | May 10, 2026, 4:33 a.m. |
Created at: May 3, 2026, 4:04 p.m.