Triple
T36692673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam (bronze cast) |
E906001
|
entity |
| Predicate | hasCastingTechnique |
P3047
|
FINISHED |
| Object | lost-wax casting (typical for Rodin bronzes) |
—
|
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 (typical for Rodin bronzes) | Statement: [Adam (bronze cast), hasCastingTechnique, lost-wax casting (typical for Rodin bronzes)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCastingTechnique Context triple: [Adam (bronze cast), hasCastingTechnique, lost-wax casting (typical for Rodin bronzes)]
-
A.
hasTechnique
chosen
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
B.
hasCasting
Indicates that an entity features a particular actor or set of actors in its cast.
-
C.
capableOfCasting
Indicates that an entity has the ability or power to perform a particular casting action (such as casting a spell, role, or object).
-
D.
hasCast
Indicates that a creative work features a particular group of performers or actors.
-
E.
allowedTechnique
Indicates that a particular technique or method is permitted or acceptable to use in a given context or under specified rules.
- 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffcf46fd688190907fd1ceb499a8d1 |
completed | May 10, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69ffccde2a8c81908e055e74077dbd19 |
completed | May 10, 2026, 12:10 a.m. |
Created at: May 3, 2026, 4:12 p.m.