Triple
T9731831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Hannut |
E235762
|
entity |
| Predicate | forceTypeInvolved |
P1062
|
FINISHED |
| Object | armored units |
—
|
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: armored units | Statement: [Battle of Hannut, forceTypeInvolved, armored units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forceTypeInvolved Context triple: [Battle of Hannut, forceTypeInvolved, armored units]
-
A.
forceType
chosen
Indicates the specific kind or category of force involved in an interaction or event (e.g., physical, legal, military, or other defined force classifications).
-
B.
forcesAction
Indicates that one entity compels or coerces another entity to perform a specific action or behavior.
-
C.
forcedBy
Indicates that an entity is compelled or coerced into an action or state by another entity.
-
D.
associatedForce
Indicates that there is a force linked or connected to an entity, typically representing the physical influence acting on or exerted by that entity.
-
E.
forceSensitive
Indicates that an entity has an innate connection to and ability to perceive or use a mystical or supernatural energy or power.
- 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_69ca84d0fad481909cdd45aa77416c48 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9eb3d6e4819090b3c7fb92550c57 |
completed | April 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69cd03c6ffc88190a5e9569e19122ad5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:22 p.m.