Triple
T1388616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Ghent |
E29903
|
entity |
| Predicate | restoredPrewarBoundaries |
P28201
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Treaty of Ghent, restoredPrewarBoundaries, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restoredPrewarBoundaries Context triple: [Treaty of Ghent, restoredPrewarBoundaries, true]
-
A.
territorialChange
Indicates a change in control or ownership of geographic territory from one entity to another, often as a result of political, legal, or military events.
-
B.
wasDividedByTreaty
Indicates that an entity (such as a territory or region) was partitioned or separated as the result of a formal treaty or agreement.
-
C.
hasHistoricTerritory
Indicates that an entity possesses or claims a territory that it historically occupied, controlled, or was associated with in the past.
-
D.
continentBorders
Indicates that one continent shares a land or maritime boundary directly with another continent.
-
E.
bordersToTheEast
Indicates that one entity shares a boundary with another entity and is located directly to the east of it.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c35ad578819090abf96222112bda |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4beffcf808190ab4cd0271257ce63 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c2f16ae081908c92792253f3eb4b |
completed | March 1, 2026, 10:51 p.m. |
Created at: March 1, 2026, 7:59 p.m.