Triple

T26458490
Position Surface form Disambiguated ID Type / Status
Subject Ashkhen of Armenia E665558 entity
Predicate title P38 FINISHED
Object Queen Ashkhen
Queen Ashkhen was an early 4th-century Armenian queen consort, known as the wife of King Tiridates III and a key figure in Armenia’s adoption of Christianity as a state religion.
E1725314 NE 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: Queen Ashkhen | Statement: [Ashkhen of Armenia, title, Queen Ashkhen]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Queen Ashkhen
Triple: [Ashkhen of Armenia, title, Queen Ashkhen]
Generated description
Queen Ashkhen was an early 4th-century Armenian queen consort, known as the wife of King Tiridates III and a key figure in Armenia’s adoption of Christianity as a state religion.

Provenance (5 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_69ee883e812c8190a9b5a9cdb87fee5e completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69f6129295a081909836581b21c1b416 completed May 2, 2026, 3:04 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11aed92d7c81909169b1ce21ac0697 completed May 23, 2026, 1:42 p.m.
NEDg Description generation batch_6a11afcce63c8190ac822c630de91480 completed May 23, 2026, 1:46 p.m.
NED2 Entity disambiguation (via description) batch_6a11b08396c8819094b627b21872f43b completed May 23, 2026, 1:49 p.m.
Created at: April 27, 2026, 12:10 a.m.