Triple
T25576441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yodo Castle |
E641119
|
entity |
| Predicate | originalBuilderClan |
P180197
|
FINISHED |
| Object | Toyotomi clan |
—
|
NE NERFINISHED |
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: Toyotomi clan | Statement: [Yodo Castle, originalBuilderClan, Toyotomi clan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalBuilderClan Context triple: [Yodo Castle, originalBuilderClan, Toyotomi clan]
-
A.
clanFounder
Indicates that an entity is the original creator or establisher of a particular clan.
-
B.
clanCentre
Indicates that one entity serves as the central location, headquarters, or main base for a particular clan or group.
-
C.
clanSystem
Indicates a social structure in which individuals are organized into kin-based groups (clans) that define relationships, obligations, and affiliations among them.
-
D.
clanType
Indicates the specific category or classification of a clan within a broader clan system or hierarchy.
-
E.
associatedClanChief
Indicates a relationship where an entity is linked or connected to a particular clan chief, typically as the chief responsible for or representing that entity.
- 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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
| PDg | Predicate description generation | batch_69f739a58b3c81908abc2b8738a65678 |
completed | May 3, 2026, 12:03 p.m. |
Created at: April 21, 2026, 4:01 p.m.