Triple
T28497309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ejmiatsin |
E721141
|
entity |
| Predicate | capitalOfArmeniaUntil |
P178790
|
FINISHED |
| Object | 4th century |
—
|
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: 4th century | Statement: [Ejmiatsin, capitalOfArmeniaUntil, 4th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOfArmeniaUntil Context triple: [Ejmiatsin, capitalOfArmeniaUntil, 4th century]
-
A.
historicalNameInArmenian
Indicates that an entity has a specific historical name or designation when expressed in the Armenian language.
-
B.
populationRankInArmenia
Indicates the relative position of an entity in terms of population size compared to other entities within Armenia.
-
C.
distanceFromYerevan_km
Indicates the physical distance, measured in kilometers, between a given place and the city of Yerevan.
-
D.
officialNameInArmenian
Indicates the officially recognized name of an entity as expressed in the Armenian language.
-
E.
dynasticNameInArmenian
Indicates that the specified dynastic name is expressed in the Armenian language.
- F. None of above. chosen
Provenance (4 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: April 28, 2026, 3:04 a.m.