Triple
T17330963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dotaku |
E420812
|
entity |
| Predicate | manufacturingMethod |
P35199
|
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: [Dotaku, manufacturingMethod, lost-wax casting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: manufacturingMethod Context triple: [Dotaku, manufacturingMethod, lost-wax casting]
-
A.
hasProductionMethod
chosen
Indicates that one entity is produced, created, or manufactured using the method, process, or technique specified by another entity.
-
B.
manufacturingModel
Indicates that one entity serves as the manufacturing model, design, or template according to which another entity is produced or manufactured.
-
C.
constructionMethod
Indicates the technique or process by which something is built, assembled, or created.
-
D.
traditionalProductionMethod
Indicates that something is created or carried out using long-established, customary techniques rather than modern or industrial methods.
-
E.
usesManufacturingType
Indicates that one entity produces or processes something by applying a specific type or method of manufacturing.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439d5c788819092bdc4d3de0ec958 |
completed | April 19, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:43 a.m.