Triple
T7715562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aubusson |
E174869
|
entity |
| Predicate | tapestryStyle |
P78298
|
FINISHED |
| Object | pictorial wall hangings |
—
|
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: pictorial wall hangings | Statement: [Aubusson, tapestryStyle, pictorial wall hangings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tapestryStyle Context triple: [Aubusson, tapestryStyle, pictorial wall hangings]
-
A.
stagingStyle
Indicates how an event, performance, or scene is arranged, presented, or visually organized in a given context.
-
B.
stylingFeature
Indicates a visual or design-related characteristic applied to an entity, such as formatting, layout, or aesthetic treatment.
-
C.
traditionalStyle
Indicates that something follows or embodies a conventional, long-established way of doing, making, or presenting it, in contrast to modern or innovative styles.
-
D.
structureStyle
Indicates the architectural or design style characterizing how a structure is built or formed.
-
E.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an entity.
- 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_69c6995c463c8190a14458036249d419 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702ebb7448190ae8d47fe0cbb0907 |
completed | March 27, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69c701683dec8190be9861e592aa8ce0 |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c702e9a32081909a153190a62af426 |
completed | March 27, 2026, 10:21 p.m. |
Created at: March 27, 2026, 4:04 p.m.