Triple
T24373576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andranik Eskandarian |
E614402
|
entity |
| Predicate | isOfDescent |
P95347
|
FINISHED |
| Object | Iranian-Armenian |
—
|
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: Iranian-Armenian | Statement: [Andranik Eskandarian, isOfDescent, Iranian-Armenian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOfDescent Context triple: [Andranik Eskandarian, isOfDescent, Iranian-Armenian]
-
A.
ofDescent
chosen
Indicates a genealogical or ancestral relationship, specifying that one entity descends from or originates from another.
-
B.
hasTypeOfDescent
Indicates that one entity possesses a particular kind or category of ancestral or lineage-based origin in relation to another entity.
-
C.
claimedDescentFrom
Indicates that one entity asserts or maintains that it is descended from, or originates genealogically from, another entity.
-
D.
descentFrom
Indicates that one entity is a descendant of another, typically through a lineage or ancestral relationship.
-
E.
hasDescent
Indicates that one entity is a descendant of another, typically through a lineage or ancestry relationship.
- 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_69e2d7e1e010819098b95eb3f905943d |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293d52f3481908bedc5844b3a8c5e |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:02 a.m.