Triple
T4955253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Armistice Commission |
E111265
|
entity |
| Predicate | typeOfAgreementMonitored |
P38198
|
FINISHED |
| Object | armistice |
—
|
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: armistice | Statement: [Military Armistice Commission, typeOfAgreementMonitored, armistice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAgreementMonitored Context triple: [Military Armistice Commission, typeOfAgreementMonitored, armistice]
-
A.
hasTypeOfAgreement
chosen
Indicates that one entity is associated with, or governed by, a specific category or type of agreement.
-
B.
basedOnAgreementWith
Indicates that something exists, is done, or is determined on the basis of a prior agreement or accord between the involved parties.
-
C.
monitoredFor
Indicates that one entity is being observed or tracked over time to detect, assess, or manage the occurrence or progression of another entity (such as a condition, event, or risk).
-
D.
agreementSigned
Indicates that a formal agreement or contract has been officially signed and accepted by the involved parties.
-
E.
aimOfAgreement
Indicates the intended purpose or objective that an agreement is designed to achieve.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71babb44819085b4cd4864433e79 |
completed | March 20, 2026, 4:11 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3beb008190852fd6150813b252 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:32 p.m.