Triple
T3788985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Left Bank of the Rhine |
E89597
|
entity |
| Predicate | wasRemilitarizedInYear |
P19756
|
FINISHED |
| Object | 1936 |
—
|
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: 1936 | Statement: [Left Bank of the Rhine, wasRemilitarizedInYear, 1936]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRemilitarizedInYear Context triple: [Left Bank of the Rhine, wasRemilitarizedInYear, 1936]
-
A.
remilitarizedBy
Indicates that a previously demilitarized area, zone, or entity has been restored to military status or armed forces presence by a specified actor.
-
B.
yearOfSurrender
Indicates the specific calendar year in which an entity formally surrendered or yielded, typically ending its resistance or control.
-
C.
wasMilitarized
chosen
Indicates that an entity underwent a process of being organized, equipped, or adapted for military use or purposes.
-
D.
hasMilitarySignificanceSince
Indicates that something has held military importance or strategic value starting from a specified point in time.
-
E.
reestablishedInYear
Indicates that an entity, previously existing and then discontinued or dissolved, was brought back into existence or operation in the specified year.
- 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_69aed9597d6881909b6ee3b9de859223 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecefa3608190a7a20ed6df6a64b2 |
completed | March 9, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69aee743c8d08190a9f9c97b836bd703 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:14 p.m.