Triple
T29730656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Alexandropol |
E752309
|
entity |
| Predicate | partyStatusAtSigning |
P60373
|
FINISHED |
| Object | Armenia under military occupation |
—
|
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: Armenia under military occupation | Statement: [Treaty of Alexandropol, partyStatusAtSigning, Armenia under military occupation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partyStatusAtSigning Context triple: [Treaty of Alexandropol, partyStatusAtSigning, Armenia under military occupation]
-
A.
signatoryState
Indicates that a state is a formal party to, and has signed or ratified, a specific treaty, agreement, or legal instrument.
-
B.
agreementSignedBy
Indicates that a particular agreement has been formally signed or executed by a specified party.
-
C.
partyStatusContext
chosen
Indicates the contextual status or role a party holds within a specific situation, event, or legal/transactional framework.
-
D.
legalStatusAtApproval
Indicates the legal status or classification an entity held at the time it was formally approved.
-
E.
signedStatus
Indicates whether an entity has formally signed or approved a document, agreement, or record.
- 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_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 28, 2026, 7:42 p.m.