Triple
T37172575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunnerside |
E920953
|
entity |
| Predicate | occupyingPowerInTargetArea |
P188168
|
FINISHED |
| Object | Nazi Germany |
—
|
NE NERFINISHED |
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: Nazi Germany | Statement: [Gunnerside, occupyingPowerInTargetArea, Nazi Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occupyingPowerInTargetArea Context triple: [Gunnerside, occupyingPowerInTargetArea, Nazi Germany]
-
A.
occupyingPower
Indicates that one entity holds military or political control over a territory that it does not legally own, typically as an occupying authority.
-
B.
enemyOccupation
Indicates that a location or territory is currently controlled or held by enemy forces.
-
C.
occupiedRegion
Indicates that an entity has taken control of and is currently holding a specific geographic area or region.
-
D.
heldTerritory
Indicates that one entity maintained control or possession over a specific territory or geographic area.
-
E.
occupyingForces
Indicates that one group’s military forces are present in and exercising control over a territory that is not their own, typically without the full consent of the local sovereign authority.
- 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fba28684208190921694f23e350c3b |
completed | May 6, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:15 p.m.