Triple
T24145607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carlin, Nevada |
E598373
|
entity |
| Predicate | hasNearbyMineType |
P38268
|
FINISHED |
| Object | open-pit gold mine |
—
|
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: open-pit gold mine | Statement: [Carlin, Nevada, hasNearbyMineType, open-pit gold mine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyMineType Context triple: [Carlin, Nevada, hasNearbyMineType, open-pit gold mine]
-
A.
hasNearbyMine
chosen
Indicates that one entity is located close to or in the vicinity of a mine associated with another entity.
-
B.
hasNotableNearbyEntity
Indicates that one entity has another significant or noteworthy entity located in its close physical or contextual proximity.
-
C.
hasNearbyTrailType
Indicates that one entity has another entity of a specified trail type located in close proximity to it.
-
D.
locatedInMineType
Indicates that something is situated within or associated with a specific type of mine.
-
E.
hasCoalMineNearby
Indicates that a location or entity is situated close to at least one coal mine.
- 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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e00a37b881909e31f85a667e6d83 |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:29 p.m.