Triple
T30743720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orr phase |
E782761
|
entity |
| Predicate | ceramicDecoration |
P157383
|
FINISHED |
| Object | incised decoration |
—
|
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: incised decoration | Statement: [Orr phase, ceramicDecoration, incised decoration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceramicDecoration Context triple: [Orr phase, ceramicDecoration, incised decoration]
-
A.
decoration
Indicates that one entity serves as an ornament or embellishing element for another entity, enhancing its appearance or style.
-
B.
decorativeCategory
Indicates that one entity is classified as belonging to a particular decorative style, theme, or ornamentation category of another entity.
-
C.
decorationCategory
chosen
Indicates the classification or type of decoration that an item, element, or space belongs to.
-
D.
ceramicsDistrict
Indicates that an entity is located in, associated with, or designated as a district known for ceramics production, trade, or related activities.
-
E.
decorationDesigner
Indicates that one entity is the person or agent responsible for designing the decoration of 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f6b835c8190b52471f03ebf3453 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:38 p.m.