Triple
T28498209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sasuntsi Davit |
E721163
|
entity |
| Predicate | hasHeroicLineage |
P176968
|
FINISHED |
| Object | house of Sassoun |
—
|
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: house of Sassoun | Statement: [Sasuntsi Davit, hasHeroicLineage, house of Sassoun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeroicLineage Context triple: [Sasuntsi Davit, hasHeroicLineage, house of Sassoun]
-
A.
hasBloodline
chosen
Indicates that one entity is ancestrally or genetically descended from, or belongs to the lineage of, another entity.
-
B.
hasMagicLineage
Indicates that one entity is descended from, or ancestrally connected to, another through a bloodline associated with magic or supernatural powers.
-
C.
hasPriestlyLineage
Indicates that an entity descends from, or belongs to, a recognized priestly family or hereditary priestly line.
-
D.
hasMortalOrSemiDivineAncestry
Indicates that an entity descends from, or is otherwise ancestrally connected to, beings who are mortal or possess semi-divine (partly divine) status.
-
E.
isRelictLineage
Indicates that an entity represents a surviving remnant of an otherwise extinct evolutionary lineage.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 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. |
Created at: April 28, 2026, 3:05 a.m.