Triple
T29730659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Alexandropol |
E752309
|
entity |
| Predicate | datePrecededBy |
P70149
|
FINISHED |
| Object | Sovietization of Armenia (late November 1920) |
—
|
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: Sovietization of Armenia (late November 1920) | Statement: [Treaty of Alexandropol, datePrecededBy, Sovietization of Armenia (late November 1920)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: datePrecededBy Context triple: [Treaty of Alexandropol, datePrecededBy, Sovietization of Armenia (late November 1920)]
-
A.
chronologyPrecedes
Indicates that one event or state occurs earlier in time than another in a chronological sequence.
-
B.
preDates
chosen
Indicates that one entity existed, occurred, or was established earlier in time than another entity.
-
C.
wasPrecededBy
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
D.
createdBefore
Indicates that one entity was created at an earlier time than another entity.
-
E.
predecessorStartDate
Indicates that the start date of one entity directly follows or is constrained by the start date of its predecessor entity in a sequence or dependency chain.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6732fff7c81908326c2deaffcdf86 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:42 p.m.