Triple
T834178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordic Classicism |
E18032
|
entity |
| Predicate | hasDesignPrinciple |
P532
|
FINISHED |
| Object | legible building volumes |
—
|
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: legible building volumes | Statement: [Nordic Classicism, hasDesignPrinciple, legible building volumes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesignPrinciple Context triple: [Nordic Classicism, hasDesignPrinciple, legible building volumes]
-
A.
usesPrinciple
Indicates that one entity applies, relies on, or is based upon a particular principle in its functioning, reasoning, or design.
-
B.
designPhilosophy
chosen
Indicates the guiding principles, values, or conceptual approach that shape how something is designed or created.
-
C.
typeOfPrinciples
Indicates a relationship where one entity specifies the kind or category of principles that another entity embodies, uses, or is governed by.
-
D.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
E.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
- 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_69a49389f44881909a608fb27d89f247 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abb84fe081909b8f4b4202845860 |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7c7df881909c539c3ab8ff0367 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.