Triple
T20784127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corona Graeca |
E511582
|
entity |
| Predicate | hasManufacturingTechnique |
P35199
|
FINISHED |
| Object | champlevé 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: champlevé enamel | Statement: [Corona Graeca, hasManufacturingTechnique, champlevé enamel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasManufacturingTechnique Context triple: [Corona Graeca, hasManufacturingTechnique, champlevé enamel]
-
A.
hasTechnique
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
B.
hasProductionMethod
chosen
Indicates that one entity is produced, created, or manufactured using the method, process, or technique specified by another entity.
-
C.
usesManufacturingType
Indicates that one entity produces or processes something by applying a specific type or method of manufacturing.
-
D.
hasCraft
Indicates a relationship where an entity possesses, operates, or is associated with a particular vehicle, vessel, or other craft.
-
E.
hasNotableCraft
Indicates that an entity is associated with a particularly significant or distinguished craft, skill, or artisanal practice.
- 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c28a4584819084d2d02febe47001 |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:38 p.m.