Triple
T4069438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 4 Commando |
E86607
|
entity |
| Predicate | enemyOccupiedArea |
P3259
|
FINISHED |
| Object | German-occupied France |
—
|
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: German-occupied France | Statement: [No. 4 Commando, enemyOccupiedArea, German-occupied France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enemyOccupiedArea Context triple: [No. 4 Commando, enemyOccupiedArea, German-occupied France]
-
A.
occupiedBy
Indicates that a space, position, or role is currently being used, held, or filled by a particular entity.
-
B.
occupyingPower
chosen
Indicates that one entity holds military or political control over a territory that it does not legally own, typically as an occupying authority.
-
C.
affectedArea
Indicates the specific region or extent over which an event, condition, or influence has an impact.
-
D.
defenseArea
Indicates a spatial region or zone that is designated for defensive protection or military/security defense activities.
-
E.
heldTerritory
Indicates that one entity maintained control or possession over a specific territory or geographic area.
- 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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbfa45c88190b7b13b35de816378 |
completed | March 9, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69aef9061d2481908307cafc9e9b32c0 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.