Triple
T1821467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doric order |
E40547
|
entity |
| Predicate | hasTypicalFriezePattern |
P9591
|
FINISHED |
| Object | alternating triglyphs and metopes |
—
|
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: alternating triglyphs and metopes | Statement: [Doric order, hasTypicalFriezePattern, alternating triglyphs and metopes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalFriezePattern Context triple: [Doric order, hasTypicalFriezePattern, alternating triglyphs and metopes]
-
A.
hasFrieze
chosen
Indicates that one entity features or is adorned with a frieze associated with another entity.
-
B.
hasSpiralPattern
Indicates that one entity exhibits or possesses a spiral-shaped pattern or arrangement in relation to another.
-
C.
camouflagePattern
Indicates that one entity has a surface or visual design intended to conceal it by blending with its surroundings or disrupting its outline.
-
D.
hasStreetGridPattern
Indicates that an area’s street layout follows a structured, grid-like pattern of intersecting roads.
-
E.
hasBearingPattern
Indicates a relationship where an object or system exhibits or is characterized by a specific bearing arrangement or configuration pattern.
- 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_69a8864526c081908a3a4d74f689e2c5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aba67721788190951beae25e885457 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61d884548190a19cf3a6b5ae9d48 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.