Triple
T9804308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Führer |
E237914
|
entity |
| Predicate | modernUsageStatus |
P65653
|
FINISHED |
| Object | taboo in German political discourse |
—
|
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: taboo in German political discourse | Statement: [Führer, modernUsageStatus, taboo in German political discourse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernUsageStatus Context triple: [Führer, modernUsageStatus, taboo in German political discourse]
-
A.
modernUse
Indicates how something is currently used or applied in modern times.
-
B.
modernStatus
Indicates the current or contemporary condition, classification, or standing of an entity in the present time.
-
C.
usageStatus
chosen
Indicates the current state or condition of how something is being used, such as whether it is active, inactive, available, or in use.
-
D.
contemporaryUse
Indicates that something is currently used or practiced in the present time or modern context.
-
E.
modernAccess
Indicates that an entity has contemporary, up-to-date means or methods of accessing or interacting with another entity or resource.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdab7a0ce881908f0555d194dece3f |
completed | April 1, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03dd2da881909052fbf29736a773 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:29 p.m.