Triple
T28831955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artsruni dynasty |
E728072
|
entity |
| Predicate | hasDynasticSeat |
P42447
|
FINISHED |
| Object | Vaspurakan |
—
|
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: Vaspurakan | Statement: [Artsruni dynasty, hasDynasticSeat, Vaspurakan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDynasticSeat Context triple: [Artsruni dynasty, hasDynasticSeat, Vaspurakan]
-
A.
dynasticSeat
chosen
Indicates that a particular location serves as the principal seat of power or ruling center for a specific dynasty or ruling family.
-
B.
hasDynasticFunction
Indicates that something serves a role or purpose within a dynasty, such as supporting its continuity, authority, or internal organization.
-
C.
isDynastic
Indicates that a relationship, status, or succession is based on or belongs to a hereditary ruling family or lineage.
-
D.
hasDynasticSignificance
Indicates that something holds importance or influence within the context of a dynasty’s continuity, status, or historical legacy.
-
E.
dynasticStatus
Indicates the relationship between an entity and a ruling dynasty, such as membership in, association with, or status within that dynastic line.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6593d67d48190af4c50e85c604a37 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:38 a.m.