Triple
T22251494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Émaux et camées |
E549988
|
entity |
| Predicate | mediumDepicted |
P9561
|
FINISHED |
| Object | enamel |
—
|
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: enamel | Statement: [Émaux et camées, mediumDepicted, enamel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediumDepicted Context triple: [Émaux et camées, mediumDepicted, enamel]
-
A.
mediumDepictedIn
Indicates that a particular medium or material is represented, shown, or referenced within another work or depiction.
-
B.
mediumDisplayed
Indicates that a particular medium (such as an image, video, or document) is being shown or rendered in a given context or interface.
-
C.
depictsMedium
chosen
Indicates that one entity visually represents or portrays the medium or material of another entity.
-
D.
mediumAdaptedTo
Indicates that a medium (such as a format, channel, or platform) has been specifically adjusted or tailored to suit a particular use, context, or target.
-
E.
medium
Indicates that an entity serves as the means, channel, or intermediary through which an action, communication, or effect is carried out between other entities.
- 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_69e11e41d9408190bd770cf282e22753 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f138befa208190877760dec1896740 |
completed | April 28, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
Created at: April 16, 2026, 8:39 p.m.