Triple
T29108955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waregem |
E736839
|
entity |
| Predicate | hasWorldWarISite |
P90634
|
FINISHED |
| Object | Flanders Field American Cemetery and Memorial |
—
|
NE NERFINISHED |
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: Flanders Field American Cemetery and Memorial | Statement: [Waregem, hasWorldWarISite, Flanders Field American Cemetery and Memorial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorldWarISite Context triple: [Waregem, hasWorldWarISite, Flanders Field American Cemetery and Memorial]
-
A.
hasWorldWarIIAssociation
Indicates that there is a notable connection or relevance between an entity and World War II, such as involvement, impact, or contextual association.
-
B.
warRelatedSite
chosen
Indicates a site that is associated with, used in, or significantly affected by a war or armed conflict.
-
C.
hasPrimaryTheatreOfWar
Indicates that an armed conflict or military operation is chiefly conducted within a particular geographic theatre or region of war.
-
D.
worldWarIService
Indicates that an entity served or participated in military service during World War I.
-
E.
worldWarIPartOf
Indicates that an event or entity is a component, phase, or subset of World War I.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 28, 2026, 11:17 a.m.