Triple
T28437833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Plussa |
E715618
|
entity |
| Predicate | durationOfTruce |
P63241
|
FINISHED |
| Object | 3 years |
—
|
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: 3 years | Statement: [Treaty of Plussa, durationOfTruce, 3 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: durationOfTruce Context triple: [Treaty of Plussa, durationOfTruce, 3 years]
-
A.
ceasefireDuration
chosen
Indicates the length of time for which a ceasefire agreement between parties is intended to remain in effect.
-
B.
peaceDuration
Indicates the length of time during which a state of peace exists or is maintained between entities.
-
C.
timeBetweenPeaceAndWarResumption
Indicates the duration of time that elapses between a period of peace and the resumption of war or armed conflict.
-
D.
hasCapitalDuringTruce
Indicates that an entity served as the capital of another entity specifically during a defined truce period.
-
E.
ceasefireDate
Indicates the date on which a ceasefire between parties is formally initiated, agreed, or comes into effect.
- 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64e3b35fc819096c20346642c2a38 |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:44 a.m.