Triple
T32783622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ypres Reservoir Cemetery |
E838424
|
entity |
| Predicate | hasPostwarConcentration |
P198046
|
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: [Ypres Reservoir Cemetery, hasPostwarConcentration, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostwarConcentration Context triple: [Ypres Reservoir Cemetery, hasPostwarConcentration, yes]
-
A.
postWarOccupation
Indicates that one entity occupied, administered, or controlled another entity or territory in the period following a war.
-
B.
hasPostwarArchitecture
Indicates that an entity possesses architectural features or structures that were designed or built in the period following a major war, typically reflecting postwar styles or reconstruction efforts.
-
C.
hasPostWarIssues
Indicates that an entity experiences problems, challenges, or complications that arise in the period following a war or major conflict.
-
D.
statusAfter1942
Indicates the status or condition of an entity as it existed after the year 1942.
-
E.
postwarOutcome
Indicates the result or consequences that follow for a party or situation after a war has ended.
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fec4cffed08190b5e5e7cc0c87493e |
completed | May 9, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_69fec2ea7fe08190bd751b39515f69d1 |
completed | May 9, 2026, 5:15 a.m. |
| PDg | Predicate description generation | batch_69fec4cee6a081908139ea6aa608f729 |
completed | May 9, 2026, 5:23 a.m. |
Created at: May 1, 2026, 1:14 a.m.