Triple
T29764966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sendlinger Tor |
E753879
|
entity |
| Predicate | hasOriginalConstructionCentury |
P15335
|
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: [Sendlinger Tor, hasOriginalConstructionCentury, 14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalConstructionCentury Context triple: [Sendlinger Tor, hasOriginalConstructionCentury, 14th century]
-
A.
containsBuildingFromCentury
Indicates that a location or area includes at least one building that originates from a specified century.
-
B.
estimatedConstructionEndCentury
Indicates the century in which the construction of something is estimated to have been completed.
-
C.
originalCentury
chosen
Indicates the century in which something was originally created, produced, or came into existence.
-
D.
originallyErectedIn
Indicates that something was first constructed or put up in a specific place or location.
-
E.
approximateReconstructionCentury
Indicates that an entity’s reconstruction date is estimated to fall within a specified century.
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: April 28, 2026, 8:37 p.m.