Triple
T32048210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sangro Valley |
E818408
|
entity |
| Predicate | wasFrontlineDuring |
P117051
|
FINISHED |
| Object | World War II |
—
|
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: World War II | Statement: [Sangro Valley, wasFrontlineDuring, World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFrontlineDuring Context triple: [Sangro Valley, wasFrontlineDuring, World War II]
-
A.
frontLineDuring
chosen
Indicates that an entity is positioned at or serves on the front line during a specified time or event.
-
B.
wasTargetDuring
Indicates that an entity served as the target of another entity or action during a specified time period or event.
-
C.
wasIn
Indicates that an entity existed, occurred, or was located within a particular place or context during a specified time or situation.
-
D.
wasBombardedDuring
Indicates that an entity was subjected to a bombardment (e.g., shelling, bombing, or heavy attack) during a specified event or time period.
-
E.
wasMilitarizedDuring
Indicates that an entity transitioned to or adopted a military character, role, or control during a specified time period or event.
- 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4c34e2c819088c66b77fbd7dfca |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:20 a.m.