Triple
T1766516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Planning Office |
E38774
|
entity |
| Predicate | operatedInTerritory |
P6665
|
FINISHED |
| Object | occupied Poland |
—
|
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: occupied Poland | Statement: [SS Planning Office, operatedInTerritory, occupied Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedInTerritory Context triple: [SS Planning Office, operatedInTerritory, occupied Poland]
-
A.
operatedInRegion
chosen
Indicates that an entity conducted operations or activities within a specified geographic region.
-
B.
operatesToRegion
Indicates that an agent conducts operations or provides services directed toward or within a specified region.
-
C.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
-
D.
definedTerritoryOf
Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of another entity.
-
E.
operatesInCountries
Indicates that an entity conducts its activities or business within the specified countries.
- 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_69a8862d562481908d7025a1c1f67c0d |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab39fc2c448190bfaf1ee8d474632a |
completed | March 6, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69aa61cbb1288190a7ba38b61905f578 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.