Triple
T10127641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DNVP |
E226253
|
entity |
| Predicate | enteredCoalitionWith |
P58850
|
FINISHED |
| Object | NSDAP in 1933 |
—
|
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: NSDAP in 1933 | Statement: [DNVP, enteredCoalitionWith, NSDAP in 1933]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredCoalitionWith Context triple: [DNVP, enteredCoalitionWith, NSDAP in 1933]
-
A.
enteredConfederation
Indicates that an entity became a member of, or formally joined, a confederation.
-
B.
hasCoalition
Indicates that an entity participates in, belongs to, or is associated with a coalition formed with one or more other entities.
-
C.
formedCoalitionWith
chosen
Indicates that two or more parties have joined together in a formal alliance or partnership to pursue shared goals or interests.
-
D.
formedByCoalition
Indicates that something (such as a group, government, or organization) came into existence through the alliance or joint effort of multiple distinct parties or factions.
-
E.
memberOfPoliticalCoalition
Indicates that an entity belongs to or participates as a constituent member in a specific political coalition.
- 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_69ca843057b48190a86730167f5d6b98 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd2f0a0e881909267a83fbeb31f0c |
completed | April 2, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:05 p.m.