Triple
T35046095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legend of Duluoz |
E1011198
|
entity |
| Predicate | recurringSurname |
P49952
|
FINISHED |
| Object | Duluoz |
—
|
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: Duluoz | Statement: [Legend of Duluoz, recurringSurname, Duluoz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recurringSurname Context triple: [Legend of Duluoz, recurringSurname, Duluoz]
-
A.
surnameReversedFrom
Indicates that one entity’s surname is derived by reversing the character order of another entity’s surname.
-
B.
associatedSurname
chosen
Indicates that one entity has a surname that is linked or connected to another entity, such as a person, family, or name record.
-
C.
sharesSurnameWithMany
Indicates that an entity has the same surname as a large number of other entities.
-
D.
fatherSurname
Indicates that one entity has the same surname as, or is identified by, the family name of, the father in relation to another entity.
-
E.
familyNameSuffix
Indicates that one entity is the suffix portion (such as “Jr.” or “III”) of another entity’s family 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.