Triple
T22161840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unas |
E547688
|
entity |
| Predicate | causewayDecoration |
P8228
|
FINISHED |
| Object | reliefs depicting famine and trade scenes |
—
|
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: reliefs depicting famine and trade scenes | Statement: [Unas, causewayDecoration, reliefs depicting famine and trade scenes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causewayDecoration Context triple: [Unas, causewayDecoration, reliefs depicting famine and trade scenes]
-
A.
causewayType
Indicates the specific kind or classification of a causeway associated with an entity.
-
B.
ornamentationStyle
Indicates the decorative design or stylistic approach applied as ornamentation to an entity.
-
C.
causewayClaim
Indicates that one entity asserts or maintains a claim regarding rights, ownership, or control over a causeway.
-
D.
decorations
chosen
Indicates that one entity adds, provides, or serves as ornamental or decorative elements for another entity.
-
E.
decorativeFinish
Indicates that one entity serves as an ornamental or aesthetic surface treatment applied 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_69e11e3c4c5c81908d336165816b12e0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a2e47a88190a3b5c05398605f68 |
completed | April 28, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:34 p.m.