Triple
T29730639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Alexandropol |
E752309
|
entity |
| Predicate | requiredArmeniaToRenounce |
P179004
|
FINISHED |
| Object | Treaty of Sèvres |
—
|
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: Treaty of Sèvres | Statement: [Treaty of Alexandropol, requiredArmeniaToRenounce, Treaty of Sèvres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredArmeniaToRenounce Context triple: [Treaty of Alexandropol, requiredArmeniaToRenounce, Treaty of Sèvres]
-
A.
renouncedBy
Indicates that an entity has been formally rejected, disowned, or given up by another entity.
-
B.
renouncedCitizenship
Indicates that an individual has formally given up or relinquished their legal citizenship status in a particular country.
-
C.
requiredSurrenderOf
Indicates that one party is obligated to give up or relinquish something to another party.
-
D.
requiredPartyToCedeTerritory
chosen
Indicates that a party is obligated to give up, transfer, or relinquish control over a specified territory to another entity.
-
E.
reasonForRenunciation
Indicates the specific cause, motive, or circumstance that led an entity to renounce or give up something.
- 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_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
Created at: April 28, 2026, 7:42 p.m.