Triple
T19527939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saumur railway tunnel |
E488579
|
entity |
| Predicate | purposeDuringWWII |
P10702
|
FINISHED |
| Object | German military rail supply route |
—
|
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: German military rail supply route | Statement: [Saumur railway tunnel, purposeDuringWWII, German military rail supply route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeDuringWWII Context triple: [Saumur railway tunnel, purposeDuringWWII, German military rail supply route]
-
A.
statusDuringWorldWarII
Indicates the role, condition, or classification an entity had specifically during the period of World War II.
-
B.
frontDuringWWII
Indicates that an entity served as a military front or active combat theater during World War II.
-
C.
purposeDuringHolocaust
Indicates that something’s purpose, role, or intended function is specifically situated within the historical context of the Holocaust.
-
D.
WWIIUse
chosen
Indicates that one entity made use of another entity during World War II, typically for military, strategic, or wartime-related purposes.
-
E.
operatorDuringWorldWarII
Indicates that an entity operated or was active in its role during the period of World War II.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6363d43148190af25caaa57accf9b |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.