Triple
T22712572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Folgore Division |
E561639
|
entity |
| Predicate | combatCharacteristic |
P7256
|
FINISHED |
| Object | close-quarters fighting |
—
|
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: close-quarters fighting | Statement: [Folgore Division, combatCharacteristic, close-quarters fighting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatCharacteristic Context triple: [Folgore Division, combatCharacteristic, close-quarters fighting]
-
A.
battleCharacteristic
Indicates a relationship where a specific trait, quality, or feature is attributed to a battle or combat scenario.
-
B.
militaryCharacteristic
chosen
Indicates that one entity possesses a specific military-related attribute, quality, or feature in relation to another entity or context.
-
C.
squadCharacteristic
Indicates that a particular characteristic, trait, or property is attributed to a squad as a whole.
-
D.
missionCharacteristic
Indicates that a mission possesses a specific attribute, feature, or quality that characterizes its nature or execution.
-
E.
weaponFeature
Indicates that one entity is a characteristic, attribute, or functional aspect of a weapon.
- 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_69e2454f1348819088d83f420925a5c1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1790ab6208190a342f076002324ab |
completed | April 29, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:18 p.m.