Triple
T28284909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uda Genji |
E713255
|
entity |
| Predicate | usesClanSurname |
P68996
|
FINISHED |
| Object | Minamoto |
—
|
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: Minamoto | Statement: [Uda Genji, usesClanSurname, Minamoto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesClanSurname Context triple: [Uda Genji, usesClanSurname, Minamoto]
-
A.
hasClanName
chosen
Indicates that an entity bears or is associated with a particular clan name.
-
B.
usedAsSurname
Indicates that something functions as a family name borne by a person or group of people.
-
C.
usedWithSurname
Indicates that something (typically a given name or title) is used together with a particular surname in naming or reference.
-
D.
hasBaseSurname
Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
-
E.
clanChiefFamilyName
Indicates that the object is the family name (surname) of the clan chief associated with the subject.
- 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 27, 2026, 11:25 p.m.