Triple
T22250176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Smart |
E549952
|
entity |
| Predicate | hasBeenQuarried |
P147551
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mount Smart, hasBeenQuarried, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenQuarried Context triple: [Mount Smart, hasBeenQuarried, yes]
-
A.
hasQuarries
Indicates that one entity possesses, contains, or is associated with one or more quarries used for extracting stone or similar materials.
-
B.
quarriedFor
Indicates that a location or source is excavated or mined in order to obtain a particular material or resource.
-
C.
eraOfQuarrying
Indicates the historical time period during which quarrying activity took place at a given site or for a given material.
-
D.
hasOpenPitMine
Indicates that an entity operates, contains, or is associated with an open-pit mining site.
-
E.
historicallyQuarriedIn
Indicates that a material or resource was extracted from a particular location during a past historical period.
- 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_69e11e41d9408190bd770cf282e22753 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f138bd45e88190919660d50c0b94bc |
completed | April 28, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:39 p.m.