Triple
T2063937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Column of Marcus Aurelius |
E45853
|
entity |
| Predicate | hasReliefType |
P22470
|
FINISHED |
| Object | spiral relief |
—
|
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: spiral relief | Statement: [Column of Marcus Aurelius, hasReliefType, spiral relief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReliefType Context triple: [Column of Marcus Aurelius, hasReliefType, spiral relief]
-
A.
hasRelief
Indicates that one entity features or exhibits a raised or sculpted surface design (relief) in relation to another entity or context.
-
B.
hasReliefFeature
chosen
Indicates that one entity possesses or includes a specific relief-related physical feature or characteristic.
-
C.
hasReliefOf
Indicates that one entity features, bears, or is adorned with a sculpted or carved relief representation of another entity.
-
D.
relievedBy
Indicates that one entity eases, reduces, or removes the burden, pain, stress, or responsibility experienced by another entity.
-
E.
reliefGranted
Indicates that a requested form of assistance, exemption, or remedy has been officially approved and provided.
- 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_69a8891b38288190abd572ccad9b6928 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9d3a92081909416c1d087876e99 |
completed | March 7, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69abb7aee9b48190999620176e3a6ee2 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:40 p.m.