Triple
T35146730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunn Ancient |
E1014857
|
entity |
| Predicate | hasHistoricalStyle |
P101869
|
FINISHED |
| Object | traditional Scottish design |
—
|
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: traditional Scottish design | Statement: [Gunn Ancient, hasHistoricalStyle, traditional Scottish design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalStyle Context triple: [Gunn Ancient, hasHistoricalStyle, traditional Scottish design]
-
A.
hasHistoricRegionStyle
chosen
Indicates that an entity exhibits or is characterized by the architectural or cultural style associated with a particular historic region.
-
B.
hasHistoricity
Indicates that something possesses historical existence, significance, or authenticity, rather than being purely fictional, mythical, or timeless.
-
C.
hasHistoricalCategory
Indicates that something is associated with a particular historical classification, period, or type based on its past context or significance.
-
D.
hasHistoricFeatures
Indicates that something possesses characteristics, elements, or attributes of historical significance.
-
E.
hasHistoricalSection
Indicates that something includes a dedicated part or segment that presents historical information or context.
- 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 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 3, 2026, 4:02 p.m.