Triple
T1884764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ionic order |
E39937
|
entity |
| Predicate | friezeFeature |
P9591
|
FINISHED |
| Object | continuous sculpted frieze |
—
|
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: continuous sculpted frieze | Statement: [Ionic order, friezeFeature, continuous sculpted frieze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: friezeFeature Context triple: [Ionic order, friezeFeature, continuous sculpted frieze]
-
A.
hasFrieze
chosen
Indicates that one entity features or is adorned with a frieze associated with another entity.
-
B.
exhibition
Indicates that an entity is organizing, hosting, or serving as a public display or presentation of another entity (such as artworks, objects, or information).
-
C.
featuredIn
Indicates that one entity appears or is prominently included within another entity, such as a person, work, or item being showcased in a larger work, event, or context.
-
D.
exhibitionSource
Indicates the origin or provider from which an exhibition or displayed work is sourced or obtained.
-
E.
exhibitedWith
Indicates that two or more entities were presented or displayed together as part of the same exhibition or show.
- 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.