Triple
T696327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bombing of Guernica |
E13901
|
entity |
| Predicate | targetedPopulation |
P17586
|
FINISHED |
| Object | Basque civilians |
—
|
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: Basque civilians | Statement: [Bombing of Guernica, targetedPopulation, Basque civilians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetedPopulation Context triple: [Bombing of Guernica, targetedPopulation, Basque civilians]
-
A.
supportedPopulation
Indicates that one entity provides assistance, resources, or services to sustain or benefit a specified group of people.
-
B.
populationClass
Indicates a categorical classification of a population based on shared characteristics, status, or demographic criteria.
-
C.
populationIncludes
Indicates that a population contains or encompasses the specified individual(s) or subgroup(s) as members or elements.
-
D.
hasPopulationType
Indicates that an entity’s population is classified according to a specific type or category (e.g., demographic, biological, or statistical grouping).
-
E.
populationRole
Indicates the role or function that an entity has within a population or demographic context.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0c5f51c8190acc4915099e4b384 |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d23e0a08190b08be9d1eff2a1bb |
completed | March 1, 2026, 8:10 p.m. |
| PDg | Predicate description generation | batch_69a49df19c9481909cc9bc33ed7f011b |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:36 p.m.