Triple
T10694919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weißenfels |
E252109
|
entity |
| Predicate | periodAsDucalResidence |
P95333
|
FINISHED |
| Object | 1656–1718 |
—
|
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: 1656–1718 | Statement: [Weißenfels, periodAsDucalResidence, 1656–1718]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodAsDucalResidence Context triple: [Weißenfels, periodAsDucalResidence, 1656–1718]
-
A.
usedAsRoyalResidenceUntil
Indicates that something served as a royal residence up to a specified point in time.
-
B.
servedRoyalResidence
Indicates that an entity functioned as an official residence used by royalty.
-
C.
endDateAsPrincipalRoyalResidence
Indicates the date on which a location ceased to serve as the primary royal residence.
-
D.
startDateAsPrincipalRoyalResidence
Indicates the date on which a location first began serving as the primary royal residence.
-
E.
becameRoyalResidenceIn
Indicates that a place or building started serving as an official royal residence at a specified point in time.
- F. None of above. chosen
Provenance (4 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd39c3788190bb7cd0acf8b6efdd |
completed | April 9, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8cc0788190b4c02a772e4b58b3 |
completed | April 8, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69d6df47899481909ac0e518d94883cb |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 9:11 p.m.