Triple
T36167122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alex Steiner |
E1046035
|
entity |
| Predicate | setInRegime |
P55826
|
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: [Alex Steiner, setInRegime, Nazi Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInRegime Context triple: [Alex Steiner, setInRegime, Nazi Germany]
-
A.
settingRegime
Indicates the regulatory, policy, or rule-based framework under which an action, process, or relationship is carried out.
-
B.
useRegime
Indicates a relationship where a particular method, system, or set of rules is applied or followed in carrying out an action or process.
-
C.
occursInRegime
chosen
Indicates that an event, process, or phenomenon takes place within a specific regime, context, or operating condition.
-
D.
createdRegimeOf
Indicates that one entity brought about, established, or was responsible for the formation of a particular regime or system of rule for another entity.
-
E.
setInState
Indicates that an entity is located within, or belongs to, a particular state or state-level jurisdiction.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.