Triple
T21785174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halen |
E537816
|
entity |
| Predicate | Battle of Halen |
P145927
|
FINISHED |
| Object | tookPlaceIn 1914 |
—
|
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: tookPlaceIn 1914 | Statement: [Halen, Battle of Halen, tookPlaceIn 1914]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Battle of Halen Context triple: [Halen, Battle of Halen, tookPlaceIn 1914]
-
A.
battleWasPartOf
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
-
B.
battleAlsoKnownAs
Indicates that a particular battle is known by an alternative name or names.
-
C.
battleOccurredNear
Indicates that a battle took place in spatial proximity to a specified location or entity.
-
D.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
E.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
- 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f04630f4f08190910b9e499a4249ca |
completed | April 28, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 6:52 p.m.