Triple
T25393826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Ōgimachi |
E636236
|
entity |
| Predicate | recognizedClan |
P68996
|
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: [Emperor Ōgimachi, recognizedClan, Toyotomi clan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedClan Context triple: [Emperor Ōgimachi, recognizedClan, Toyotomi clan]
-
A.
associatedClan
Indicates a relationship where an entity is linked or belongs to a particular clan, group, or lineage.
-
B.
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.
-
C.
receivedClanNameFrom
Indicates that one entity obtained or was given its clan name from another entity.
-
D.
clanSystem
Indicates a social structure in which individuals are organized into kin-based groups (clans) that define relationships, obligations, and affiliations among them.
-
E.
hasClanName
chosen
Indicates that an entity bears or is associated with a particular clan name.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 21, 2026, 1:49 p.m.