Triple
T22820845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mudanya |
E565224
|
entity |
| Predicate | armisticeRole |
P149874
|
FINISHED |
| Object | ended the Greco-Turkish War (1919–1922) |
—
|
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: ended the Greco-Turkish War (1919–1922) | Statement: [Mudanya, armisticeRole, ended the Greco-Turkish War (1919–1922)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armisticeRole Context triple: [Mudanya, armisticeRole, ended the Greco-Turkish War (1919–1922)]
-
A.
statusOfArmistice
Indicates the current condition or standing of an armistice agreement between parties.
-
B.
armisticeSignedWith
Indicates that a formal agreement to stop fighting (an armistice) has been concluded between the two related parties.
-
C.
signedArmistice
Indicates that an entity formally agreed to and endorsed an armistice, marking the suspension of active hostilities between conflicting parties.
-
D.
peacetimeRole
Indicates the role, function, or duties an entity holds during periods of peace rather than during wartime or conflict.
-
E.
opponentAfterArmistice
Indicates that one entity is the opponent of another in the period following an armistice.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17dcffdd88190a5f9c780c71b5053 |
completed | April 29, 2026, 3:41 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb577e2081909f4a4e9c296535c0 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:33 p.m.