Triple
T1215321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Reich |
E26094
|
entity |
| Predicate | onePartyState |
P25069
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Third Reich, onePartyState, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onePartyState Context triple: [Third Reich, onePartyState, true]
-
A.
inState
Indicates that an entity is currently located within or belongs to a particular state or condition.
-
B.
memberStateSide1
Indicates that an entity participates as the first member state (or party) on one side of a bilateral or multilateral relationship or agreement.
-
C.
negotiatingParty
Indicates that an entity is actively involved as a participant in a negotiation process with another entity.
-
D.
cooperatingState
Indicates that one state collaborates or works jointly with another state toward shared goals or activities.
-
E.
opponentState
Indicates the condition or status that an opposing party or competitor is currently in within a given context or interaction.
- 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_69a4948331fc8190b531ac9bec71c491 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be0370b4819093618930f4eecfcc |
completed | March 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69a4bb62a7c08190a79dcb6ff72ac99b |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bc6d5b7881908091e40c8695ef53 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:46 p.m.