Triple
T33827659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dundas House |
E867000
|
entity |
| Predicate | belongsToArchitecturalPeriod |
P103862
|
FINISHED |
| Object | 18th century architecture |
—
|
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: 18th century architecture | Statement: [Dundas House, belongsToArchitecturalPeriod, 18th century architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToArchitecturalPeriod Context triple: [Dundas House, belongsToArchitecturalPeriod, 18th century architecture]
-
A.
timePeriodOfArchitecture
chosen
Indicates the historical time period or era during which a particular architectural work, style, or feature was created or predominantly used.
-
B.
locatedInHistoricPeriod
Indicates that an entity exists, occurs, or is situated within a specific historic period or era.
-
C.
hasMonumentInPeriod
Indicates that a monument is associated with or existed during a specified time period.
-
D.
hasArchaeologicalRemainsFromPeriod
Indicates that an entity contains or preserves archaeological remains originating from a specified historical period.
-
E.
architecturalOrigin
Indicates the place, style, or tradition from which an architectural work or design originates.
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff32b88bf48190b45afd1b60cb511c |
completed | May 9, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69ff3031e18881908927b2ab452de863 |
completed | May 9, 2026, 1:01 p.m. |
Created at: May 1, 2026, 1:46 a.m.