Triple
T10333734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collegiate Church, Castle and Old Town of Quedlinburg |
E242942
|
entity |
| Predicate | containsBuildingFromCentury |
P93743
|
FINISHED |
| Object | 14th century |
—
|
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: 14th century | Statement: [Collegiate Church, Castle and Old Town of Quedlinburg, containsBuildingFromCentury, 14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsBuildingFromCentury Context triple: [Collegiate Church, Castle and Old Town of Quedlinburg, containsBuildingFromCentury, 14th century]
-
A.
constructionCentury
Indicates the century during which something was constructed or built.
-
B.
locatedInBuildingConstructedInCentury
Indicates that something is located in a building whose construction dates to a specified century.
-
C.
existedInCentury
Indicates that an entity existed or was present during a specified century.
-
D.
rebuiltInCentury
Indicates that an existing structure or entity was reconstructed or significantly rebuilt during a specified century.
-
E.
hasCloisterFromCentury
Indicates that an entity possesses a cloister that dates from, or was constructed in, a specified century.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e91fdb2081909866c6ecf417d75a |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4df9dc3208190bf1bd106f44f6202 |
completed | April 7, 2026, 10:42 a.m. |
| PDg | Predicate description generation | batch_69d4e91ce2008190af252c140370b7f2 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 11:53 a.m.