Triple
T29455956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armenian Revolutionary Federation |
E747100
|
entity |
| Predicate | relegalizedYear |
P9113
|
FINISHED |
| Object | 1990 |
—
|
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: 1990 | Statement: [Armenian Revolutionary Federation, relegalizedYear, 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relegalizedYear Context triple: [Armenian Revolutionary Federation, relegalizedYear, 1990]
-
A.
legalizationYear
Indicates the year in which something (typically an activity, substance, or status) was officially made legal by law.
-
B.
dateAbolished
Indicates the date on which something (such as an institution, law, practice, or position) was officially ended or abolished.
-
C.
repudiatedInYear
Indicates that the relationship or agreement was formally rejected, renounced, or disowned in the specified year.
-
D.
reestablishedInYear
chosen
Indicates that an entity, previously existing and then discontinued or dissolved, was brought back into existence or operation in the specified year.
-
E.
sanctionYear
Indicates the year in which a sanction was imposed, enacted, or came into effect.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66b6c26a481908018e663aee7b269 |
completed | May 2, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 3:36 p.m.