Triple
T20990256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Kardis |
E517001
|
entity |
| Predicate | confirmedStatusQuoAnteBellum |
P77049
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Treaty of Kardis, confirmedStatusQuoAnteBellum, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confirmedStatusQuoAnteBellum Context triple: [Treaty of Kardis, confirmedStatusQuoAnteBellum, yes]
-
A.
restoredStatusQuoAnte
chosen
Indicates that a prior state of affairs or original condition has been re-established after a change, disruption, or intervention.
-
B.
legalStatusAfterWar
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
-
C.
preColonialStatus
Indicates the condition, role, or social-political standing an entity held prior to the onset of colonial rule.
-
D.
confirmedTreaty
Indicates that an entity has formally approved, ratified, or validated a treaty, making the agreement officially recognized or in force.
-
E.
prewarStatus
Indicates the condition, role, or circumstances of an entity as they existed before a specific war or armed conflict.
- 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fbe5f49c8190a5c031eceba9ebf7 |
completed | April 21, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:49 p.m.