Triple
T10898563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kennedy Mine |
E257372
|
entity |
| Predicate | oreProcessingMethod |
P62247
|
FINISHED |
| Object | stamp mill |
—
|
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: stamp mill | Statement: [Kennedy Mine, oreProcessingMethod, stamp mill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oreProcessingMethod Context triple: [Kennedy Mine, oreProcessingMethod, stamp mill]
-
A.
originProcess
Indicates the process, activity, or mechanism from which an entity, condition, or outcome originally arises or is produced.
-
B.
requiresProcessingBy
Indicates that one entity must undergo handling, treatment, or transformation performed by another entity before a condition is met or a process can continue.
-
C.
usesComputationMethod
Indicates that an entity performs its processing or decision-making by applying a specified computational method or algorithm.
-
D.
realizationMethod
chosen
Indicates the means, process, or technique by which something is carried out, implemented, or brought into effect.
-
E.
processingUse
Indicates that one entity uses or applies another entity as part of a processing or transformation activity.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75d03a3fc81908df039b9b5ab9ca2 |
completed | April 9, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69d70d3d69e08190bb369e9a7927142c |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.