Triple
T32742169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Die Auferstehung |
E837244
|
entity |
| Predicate | hasTextInPublicDomain |
P95315
|
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: [Die Auferstehung, hasTextInPublicDomain, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTextInPublicDomain Context triple: [Die Auferstehung, hasTextInPublicDomain, true]
-
A.
isPublicDomain
Indicates that the subject is not protected by intellectual property rights and can be freely used, copied, and distributed by anyone.
-
B.
hasHistoricalText
Indicates that an entity is associated with a historical written document or record describing it or its past.
-
C.
inThePublicDomain
Indicates that the subject is not protected by intellectual property rights and may be freely used, copied, or distributed by anyone.
-
D.
hasTextualCorpus
chosen
Indicates that an entity is associated with or possesses a collection of written or textual materials.
-
E.
hasNotableCorpus
Indicates that an entity possesses a significant, well-recognized body of work, texts, or collected materials associated with it.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 1, 2026, 1:12 a.m.