Triple
T37287762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Mile |
E925579
|
entity |
| Predicate | hasProcessing |
P1410
|
FINISHED |
| Object | gold milling |
—
|
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: gold milling | Statement: [Golden Mile, hasProcessing, gold milling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProcessing Context triple: [Golden Mile, hasProcessing, gold milling]
-
A.
hasProcess
chosen
Indicates that an entity is associated with, participates in, or is characterized by a particular process.
-
B.
isProcessedBy
Indicates that an entity undergoes some form of handling, transformation, or treatment performed by another entity or agent.
-
C.
hasReprocessingActivity
Indicates that an entity engages in or is associated with an activity that reprocesses materials, resources, or products.
-
D.
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.
-
E.
hasSettlementProcess
Indicates a relationship where one entity uses or is governed by a particular process or procedure for settling, resolving, or concluding transactions, obligations, or disputes.
- 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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.