Triple
T29764967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sendlinger Tor |
E753879
|
entity |
| Predicate | hasOriginalConstructionMaterial |
P112113
|
FINISHED |
| Object | brick |
—
|
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: brick | Statement: [Sendlinger Tor, hasOriginalConstructionMaterial, brick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalConstructionMaterial Context triple: [Sendlinger Tor, hasOriginalConstructionMaterial, brick]
-
A.
eraOfOriginalMaterial
Indicates the historical time period during which the original material associated with an entity was created or produced.
-
B.
roofMaterialOriginal
Indicates the material that was originally used to construct the roof of a structure.
-
C.
hasArchitecturalMaterial
chosen
Indicates that something is constructed from, incorporates, or is characterized by a particular architectural material.
-
D.
originalMaterialFor
Indicates that one entity serves as the source or basis material from which another entity is derived, adapted, or created.
-
E.
reconstructionUsedOriginalMaterials
Indicates that a reconstruction was carried out using the same physical materials as those of the original object or structure.
- 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_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 28, 2026, 8:37 p.m.