Triple
T21785404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Netherlands–Germany–Belgium tripoint |
E537821
|
entity |
| Predicate | changedConfigurationInYear |
P145928
|
FINISHED |
| Object | 1919 |
—
|
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: 1919 | Statement: [Netherlands–Germany–Belgium tripoint, changedConfigurationInYear, 1919]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedConfigurationInYear Context triple: [Netherlands–Germany–Belgium tripoint, changedConfigurationInYear, 1919]
-
A.
changesEvery
Indicates that one entity undergoes a change whenever or each time another specified condition, event, or entity changes.
-
B.
pastSettingYear
Indicates that an event, narrative, or situation is set in or associated with a specific year in the past.
-
C.
changedUnder
Indicates that one entity has undergone alteration, modification, or transformation as a result of the influence, action, or conditions imposed by another entity.
-
D.
replacedInYear
Indicates that one entity took the place of or superseded another entity in a specific calendar year.
-
E.
replacedEachYear
Indicates that one entity is substituted or exchanged for another on a yearly basis.
- 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f04630f4f08190910b9e499a4249ca |
completed | April 28, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 6:52 p.m.