Triple
T38410180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ailsa Craig Common Green granite |
E901451
|
entity |
| Predicate | quarryingCountry |
P176629
|
FINISHED |
| Object | United Kingdom |
—
|
NE NERFINISHED |
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: United Kingdom | Statement: [Ailsa Craig Common Green granite, quarryingCountry, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: quarryingCountry Context triple: [Ailsa Craig Common Green granite, quarryingCountry, United Kingdom]
-
A.
historicallyQuarriedIn
Indicates that a material or resource was extracted from a particular location during a past historical period.
-
B.
quarriedFor
Indicates that a location or source is excavated or mined in order to obtain a particular material or resource.
-
C.
quarriedNear
Indicates that a material or resource was extracted from a quarry located close to a specified place or feature.
-
D.
quarryRegion
Indicates that a specified region is the location where quarrying or extraction activities take place.
-
E.
quarrySource
chosen
Indicates that one entity serves as the extraction site or origin location from which another entity (typically a material or resource) is quarried.
- 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_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. |
Created at: May 3, 2026, 4:31 p.m.