Triple
T8365986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaspurakan |
E197126
|
entity |
| Predicate | endedAsIndependentKingdom |
P43452
|
FINISHED |
| Object | 1021 |
—
|
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: 1021 | Statement: [Vaspurakan, endedAsIndependentKingdom, 1021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endedAsIndependentKingdom Context triple: [Vaspurakan, endedAsIndependentKingdom, 1021]
-
A.
endedAsPrincipality
Indicates that an entity’s existence or historical development concluded with it having the political status of a principality.
-
B.
wasKingdomUntil
Indicates that an entity functioned as a kingdom governing another entity up to a specified end time or event.
-
C.
gainedIndependenceAs
Indicates that an entity achieved political or administrative independence in the specific form, status, or identity denoted by another entity.
-
D.
foundedAsKingdom
Indicates that an entity was originally established or created in the form of a kingdom.
-
E.
wasIndependentUntil
chosen
Indicates that an entity possessed independent status or autonomy up to a specific point in time, after which that independence ceased.
- 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_69ca82f2dbe48190aba982e75a0d94de |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb808bc22481909ce2f8b48cc95806 |
completed | March 31, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69cb70cd04b08190ab5f72afd22a7967 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6 p.m.