Triple
T22008053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Lead of Ohio |
E543501
|
entity |
| Predicate | processedMaterial |
P1272
|
FINISHED |
| Object | uranium ore concentrates |
—
|
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: uranium ore concentrates | Statement: [National Lead of Ohio, processedMaterial, uranium ore concentrates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: processedMaterial Context triple: [National Lead of Ohio, processedMaterial, uranium ore concentrates]
-
A.
processedTo
Indicates that one entity is transformed or converted into another entity through some processing operation.
-
B.
processingUse
Indicates that one entity uses or applies another entity as part of a processing or transformation activity.
-
C.
performedMaterialFrom
Indicates that an agent executed or presented a performance using or based on a particular material or source work.
-
D.
materialUsed
chosen
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
E.
materialFormedIn
Indicates that a material is created, produced, or formed within a specified process, environment, or context.
- 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_69e11e2db934819095556760c7d85e4d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127a2aebc8190951ee0bf9fd8e16d |
completed | April 28, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:21 p.m.