Triple
T37172550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telavåg |
E920952
|
entity |
| Predicate | occupationForce |
P71829
|
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: [Telavåg, occupationForce, Nazi Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occupationForce Context triple: [Telavåg, occupationForce, Nazi Germany]
-
A.
occupyingForces
chosen
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.
-
B.
occupationForcesCommandedBy
Indicates that a particular occupation force is under the command or authority of a specified commander or commanding entity.
-
C.
garrisonedForce
Indicates that a military force is stationed in and occupies a specific location, typically for defense or control.
-
D.
enemyOccupation
Indicates that a location or territory is currently controlled or held by enemy forces.
-
E.
commandingForceSize
Indicates the size or magnitude of the military or organizational force that is exercising command or control in a given context.
- 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:15 p.m.