Triple
T4741685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Saint-Lô |
E105257
|
entity |
| Predicate | effectOnCity |
P53074
|
FINISHED |
| Object | devastation of Saint-Lô |
—
|
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: devastation of Saint-Lô | Statement: [Battle of Saint-Lô, effectOnCity, devastation of Saint-Lô]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnCity Context triple: [Battle of Saint-Lô, effectOnCity, devastation of Saint-Lô]
-
A.
affectedCity
Indicates that a particular city is impacted or influenced by a specified event, action, or condition.
-
B.
eventEffect
chosen
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
-
C.
cityOfInfluence
Indicates the city that significantly shapes, impacts, or exerts influence over a given entity.
-
D.
placeOfEffect
Indicates the location or setting where an action, event, or effect takes place or is realized.
-
E.
effectOnSystem
Indicates the influence, change, or impact that one entity, action, or condition has on the state or behavior of a system.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64a7153881909eac451fc7566d25 |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.