Triple
T4102680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nazi Party Rally Grounds |
E87975
|
entity |
| Predicate | firstMajorRallyHeld |
P6468
|
FINISHED |
| Object | 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: 1933 | Statement: [Nazi Party Rally Grounds, firstMajorRallyHeld, 1933]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMajorRallyHeld Context triple: [Nazi Party Rally Grounds, firstMajorRallyHeld, 1933]
-
A.
firstMajorRallyYear
chosen
Indicates the calendar year in which an entity held its first significant rally or major organized gathering.
-
B.
firstMajorModernCommemoration
Indicates that the subject marks the earliest significant contemporary event or observance formally dedicated to commemorating the object.
-
C.
isFirstMajorBattleOf
Indicates that a battle is the earliest significant or primary large-scale engagement within a particular war, campaign, or conflict.
-
D.
firstMajorUprisingEndDate
Indicates the date on which the first major uprising associated with the subject came to an end.
-
E.
notableRally
Indicates a rally or gathering that is distinguished by particular significance, impact, or prominence compared to ordinary rallies.
- 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_69aed94564cc8190a9c1457daedb6e7f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd116dac8190952cb2ddf63216ec |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90b2ef08190ae84febfd69dd48b |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:40 p.m.