Triple
T30541256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ornament and Crime |
E777285
|
entity |
| Predicate | positionOnOrnament |
P196081
|
FINISHED |
| Object | ornament is unnecessary |
—
|
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: ornament is unnecessary | Statement: [Ornament and Crime, positionOnOrnament, ornament is unnecessary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnOrnament Context triple: [Ornament and Crime, positionOnOrnament, ornament is unnecessary]
-
A.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
B.
positionOnDesign
Indicates the spatial placement or alignment of one element relative to a specific design or layout.
-
C.
positionOnPillar
Indicates that one entity is located on top of or supported by a pillar.
-
D.
positionOfEmblem
Indicates the spatial placement or location of an emblem relative to a reference object or surface.
-
E.
positionInWreath
Indicates the specific location or ordering of an element within a circular wreath arrangement.
- F. None of above. chosen
Provenance (4 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_69f2249d183c8190b79937c1768d2163 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
| PDg | Predicate description generation | batch_69fe066b623c819085205fbea901e3cf |
completed | May 8, 2026, 3:51 p.m. |
Created at: April 29, 2026, 8:19 p.m.