Triple
T35287304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Stavanger |
E1019120
|
entity |
| Predicate | hasNotableArchitecturePeriod |
—
|
GENERATED |
| Object | 18th century |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableArchitecturePeriod Context triple: [Old Stavanger, hasNotableArchitecturePeriod, 18th century]
-
A.
hasNotableArchitecturalFamily
Indicates that an entity is associated with a prominent or historically significant family known for its architectural work or legacy.
-
B.
hasMonumentInPeriod
Indicates that a monument is associated with or existed during a specified time period.
-
C.
timePeriodOfArchitecture
chosen
Indicates the historical time period or era during which a particular architectural work, style, or feature was created or predominantly used.
-
D.
hasArchaeologicalRemainsFromPeriod
Indicates that an entity contains or preserves archaeological remains originating from a specified historical period.
-
E.
locatedInHistoricPeriod
Indicates that an entity exists, occurs, or is situated within a specific historic period or era.
- F. None of above.
Provenance (1 batch)
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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.