Triple
T12345086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nishapuri |
E294331
|
entity |
| Predicate | typeOfDescentClaim |
P6273
|
FINISHED |
| Object | Iranian-origin lineage |
—
|
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-origin lineage | Statement: [Nishapuri, typeOfDescentClaim, Iranian-origin lineage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDescentClaim Context triple: [Nishapuri, typeOfDescentClaim, Iranian-origin lineage]
-
A.
claimedDescentFrom
Indicates that one entity asserts or maintains that it is descended from, or originates genealogically from, another entity.
-
B.
ofDescent
Indicates a genealogical or ancestral relationship, specifying that one entity descends from or originates from another.
-
C.
descentFrom
Indicates that one entity is a descendant of another, typically through a lineage or ancestral relationship.
-
D.
descentSystem
Indicates the kinship or inheritance pattern through which lineage, membership, or rights are traced (e.g., matrilineal, patrilineal, or bilateral).
-
E.
typeOfClaim
chosen
Indicates the specific category or nature of a claim being made in relation to an entity or statement.
- 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f7a4a448190aa70d66dc2f406c1 |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ecb5efc819086a3530282278bb1 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.