Triple
T10094844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radomiro Tomic |
E215837
|
entity |
| Predicate | hasSurfaceMining |
P10923
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Radomiro Tomic, hasSurfaceMining, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurfaceMining Context triple: [Radomiro Tomic, hasSurfaceMining, true]
-
A.
hasUndergroundMine
Indicates that one entity possesses, controls, or contains an underground mine associated with it.
-
B.
miningMethod
chosen
Indicates the technique or process used to extract minerals or resources from the earth.
-
C.
hasMiningActivity
Indicates that some form of mining operation or extraction activity is occurring at, involving, or associated with the referenced entity.
-
D.
hasMiningArea
Indicates that an entity possesses, controls, or is associated with a designated area where mining activities take place.
-
E.
hasMiningCommodity
Indicates that an entity is associated with, produces, or contains a specific mining-related commodity.
- 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_69ca83a4947c8190823a7495dc5d96ed |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd0784c288190967d143beca32c4b |
completed | April 2, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:02 p.m.