Triple
T454745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deutschlandlied |
E7208
|
entity |
| Predicate | hasControversialPart |
P9466
|
FINISHED |
| Object | first stanza of Deutschlandlied |
—
|
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: first stanza of Deutschlandlied | Statement: [Deutschlandlied, hasControversialPart, first stanza of Deutschlandlied]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasControversialPart Context triple: [Deutschlandlied, hasControversialPart, first stanza of Deutschlandlied]
-
A.
controversy
Indicates a situation in which there is active disagreement, dispute, or public debate between parties over a particular issue, action, or claim.
-
B.
locationOfControversy
Indicates the place or setting where a dispute, debate, or controversy occurs or is centered.
-
C.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
D.
disputedSections
chosen
Indicates that specific parts or portions of something are contested, challenged, or not mutually agreed upon between parties.
-
E.
hasNotableClaim
Indicates that an entity is associated with a significant, widely recognized statement, assertion, or claim.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef87cc7c8190a0fec933457821e2 |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede4de008190b5a6c159e741522e |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.