Triple
T26810893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhoikos |
E671988
|
entity |
| Predicate | usedArchitecturalElement |
P6684
|
FINISHED |
| Object | Ionic columns |
—
|
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: Ionic columns | Statement: [Rhoikos, usedArchitecturalElement, Ionic columns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedArchitecturalElement Context triple: [Rhoikos, usedArchitecturalElement, Ionic columns]
-
A.
architecturalUse
Indicates how a structure, space, or element is intended to be used or function within an architectural context.
-
B.
hasArchitecturalMaterial
Indicates that something is constructed from, incorporates, or is characterized by a particular architectural material.
-
C.
architectureCanUse
Indicates that a particular architecture is capable of employing, incorporating, or being built with a specified component, technique, or resource.
-
D.
hasArchitecturalFeature
chosen
Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
-
E.
architecturalOrderUsed
Indicates that a particular architectural order (e.g., Doric, Ionic, Corinthian) is employed in the design or construction of a structure or its elements.
- 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 27, 2026, 4:29 a.m.