Triple
T37948888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Athena at Assos |
E946685
|
entity |
| Predicate | architecturalFeaturesInclude |
P6684
|
FINISHED |
| Object | Ionic elements |
—
|
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 elements | Statement: [Temple of Athena at Assos, architecturalFeaturesInclude, Ionic elements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architecturalFeaturesInclude Context triple: [Temple of Athena at Assos, architecturalFeaturesInclude, Ionic elements]
-
A.
hasArchitecturalFeature
chosen
Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
-
B.
architecturalStyleIncludes
Indicates that a structure, building, or design incorporates or exemplifies a particular architectural style as one of its defining characteristics.
-
C.
architecturalElements
Indicates a relationship where certain components or features function as structural or design elements within an architectural context.
-
D.
architecturalUse
Indicates how a structure, space, or element is intended to be used or function within an architectural context.
-
E.
architecturalConcept
Indicates that one entity represents or embodies an architectural concept in relation to another entity.
- 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_69f76ef64cf08190ad3e1114b62aac67 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: May 3, 2026, 4:20 p.m.