Triple
T38410217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ailsa Craig Red Hone granite |
E901452
|
entity |
| Predicate | minedUnder |
P190855
|
FINISHED |
| Object | restricted quarrying licenses |
—
|
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: restricted quarrying licenses | Statement: [Ailsa Craig Red Hone granite, minedUnder, restricted quarrying licenses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minedUnder Context triple: [Ailsa Craig Red Hone granite, minedUnder, restricted quarrying licenses]
-
A.
minedOn
Indicates that a resource or material was extracted from a particular location or source on a specific date or time.
-
B.
isMinedIn
Indicates that a resource or material is extracted or obtained from a particular location or site.
-
C.
hasUndergroundMine
Indicates that one entity possesses, controls, or contains an underground mine associated with it.
-
D.
mineName
Indicates that an entity has or is associated with a specific mine identified by a given name.
-
E.
wasExtensivelyMinedIn
Indicates that a location or resource was subject to intensive or large-scale mining activity during a specified time or by a specified agent.
- 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_69f76e61e79c81908b787d83b46ab92b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fcd148e6d4819082c118832ecc599b |
completed | May 7, 2026, 5:52 p.m. |
Created at: May 3, 2026, 4:31 p.m.