Triple
T24763972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronze |
E619527
|
entity |
| Predicate | usedInArtTradition |
P68064
|
FINISHED |
| Object | lost-wax casting |
—
|
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: lost-wax casting | Statement: [Bronze, usedInArtTradition, lost-wax casting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInArtTradition Context triple: [Bronze, usedInArtTradition, lost-wax casting]
-
A.
paintingTradition
Indicates a stylistic or cultural school of painting to which an artwork or artist belongs.
-
B.
hasUseInTradition
chosen
Indicates that something is employed or holds a functional role within a particular cultural, religious, or historical tradition.
-
C.
traditionalArtForm
Indicates that something is an established artistic practice or style that has been handed down through cultural or historical tradition.
-
D.
usesDesignTradition
Indicates that one entity creates, interprets, or operates according to the established design principles, styles, or conventions associated with another entity or tradition.
-
E.
drawsFromTradition
Indicates that something is influenced by, incorporates, or builds upon established traditions or traditional practices.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 4:28 a.m.