Triple
T1761329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odoacer |
E38663
|
entity |
| Predicate | parentEthnicBackground |
P13742
|
FINISHED |
| Object | Scirian father |
—
|
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: Scirian father | Statement: [Odoacer, parentEthnicBackground, Scirian father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentEthnicBackground Context triple: [Odoacer, parentEthnicBackground, Scirian father]
-
A.
ethnicOrigin
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
B.
hasFamilyBackgroundIn
chosen
Indicates that an entity comes from, or is associated with, a particular familial or ancestral background.
-
C.
otherEthnicGroup
Indicates that one entity belongs to a different ethnic group than the other entity.
-
D.
relatedEthnicGroup
Indicates that there is a notable ethnic connection or association between two ethnic groups, such as shared ancestry, culture, or historical ties.
-
E.
hasEthnicCharacteristic
Indicates that an entity possesses or is associated with a particular ethnic characteristic or identity.
- 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_69a8862d562481908d7025a1c1f67c0d |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab173936b4819097332ee185996bbd |
completed | March 6, 2026, 6:04 p.m. |
| PD | Predicate disambiguation | batch_69aa61c9e06c819085489e00cfe72153 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.