Triple
T1884763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ionic order |
E39937
|
entity |
| Predicate | entablatureFeature |
P6684
|
FINISHED |
| Object | three-fascia architrave |
—
|
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: three-fascia architrave | Statement: [Ionic order, entablatureFeature, three-fascia architrave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entablatureFeature Context triple: [Ionic order, entablatureFeature, three-fascia architrave]
-
A.
entablatureSimilarTo
Indicates that one entablature shares similar design, structure, or stylistic features with another entablature.
-
B.
hasTransept
Indicates that one architectural structure includes or features a transept as part of its design.
-
C.
hasArchitecturalFeature
chosen
Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
-
D.
roofFeature
Indicates that one entity is a feature, element, or characteristic that is part of or associated with a roof.
-
E.
chamberSupportedBy
Indicates that a chamber is physically held up, carried, or structurally sustained by another object or structure.
- 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_69a88633e4fc8190b7eb40463e048ec5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb4f53f408190ae30e1a12721e7d7 |
completed | March 7, 2026, 5:17 a.m. |
| PD | Predicate disambiguation | batch_69abafe497a88190a1da6af2888b71b4 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.