Triple
T27263023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maceo |
E687818
|
entity |
| Predicate | miningRole |
P162289
|
FINISHED |
| Object | regional mineral extraction |
—
|
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: regional mineral extraction | Statement: [Maceo, miningRole, regional mineral extraction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: miningRole Context triple: [Maceo, miningRole, regional mineral extraction]
-
A.
miningMethod
Indicates the technique or process used to extract minerals or resources from the earth.
-
B.
isMinedIn
Indicates that a resource or material is extracted or obtained from a particular location or site.
-
C.
connectsToMiningRegion
Indicates a relationship where something is physically or functionally linked to a mining region, such as through infrastructure, operations, or direct access.
-
D.
miningAllowed
Indicates that performing mining activities is permitted under the relevant rules or conditions.
-
E.
minerRepresents
Indicates that a miner acts on behalf of, or serves as a representative or proxy for, another entity in a given context.
- F. None of above. chosen
Provenance (4 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_69ef3557abc481908bf3c146f0f3356a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f626f07218819080448c001f01ba45 |
completed | May 2, 2026, 4:31 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f622a8fe7c819096e8a43db263a423 |
completed | May 2, 2026, 4:13 p.m. |
Created at: April 27, 2026, 10:54 a.m.