Triple
T11017551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telemark Battalion |
E260400
|
entity |
| Predicate | isRapidReactionUnit |
P96584
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Telemark Battalion, isRapidReactionUnit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRapidReactionUnit Context triple: [Telemark Battalion, isRapidReactionUnit, true]
-
A.
isCombatSupportUnit
Indicates that the unit’s primary role is to provide operational or logistical support to combat forces rather than engage directly in frontline fighting.
-
B.
hasMilitaryDesignation
Indicates that an entity is assigned a specific military-related code, title, or classification.
-
C.
isStrategicReserveFor
Indicates that one entity is held or designated as a backup or contingency resource to be used strategically in support of another entity.
-
D.
isEliteUnit
Indicates that the unit belongs to a specially trained, highly capable subgroup distinguished from regular units.
-
E.
isRegularArmyUnit
Indicates that the entity functions as a formal, organized military unit within a country's regular (non-irregular) armed forces.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797a7f4a881908232f99d18d95149 |
completed | April 9, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69d72e995e008190bbffb314129ed0cd |
completed | April 9, 2026, 4:44 a.m. |
| PDg | Predicate description generation | batch_69d732242fdc8190be77d1f730a42935 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:25 p.m.