Triple
T24763969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronze |
E619527
|
entity |
| Predicate | typicalManufacturingProcess |
P104012
|
FINISHED |
| Object | 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: casting | Statement: [Bronze, typicalManufacturingProcess, casting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalManufacturingProcess Context triple: [Bronze, typicalManufacturingProcess, casting]
-
A.
typicalProcess
chosen
Indicates that the related process is characteristic, usual, or commonly occurring for the given entity or context.
-
B.
typicalProductionType
Indicates the usual or characteristic type of production activity associated with an entity.
-
C.
manufacturingModel
Indicates that one entity serves as the manufacturing model, design, or template according to which another entity is produced or manufactured.
-
D.
hasProductionMethod
Indicates that one entity is produced, created, or manufactured using the method, process, or technique specified by another entity.
-
E.
partOfProduction
Indicates that one entity functions as a component, segment, or phase within the overall process or structure of another production.
- 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_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 18, 2026, 4:28 a.m.