Triple
T26774987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ketton stone |
E670092
|
entity |
| Predicate | hasQuarryType |
P165365
|
FINISHED |
| Object | open-pit quarry |
—
|
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 quarry | Statement: [Ketton stone, hasQuarryType, open-pit quarry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQuarryType Context triple: [Ketton stone, hasQuarryType, open-pit quarry]
-
A.
hasQuarries
Indicates that one entity possesses, contains, or is associated with one or more quarries used for extracting stone or similar materials.
-
B.
hasBeenQuarried
Indicates that a material or resource has been extracted from a quarry.
-
C.
hasMineralClass
Indicates that an entity is associated with, or categorized under, a particular mineral classification.
-
D.
hasRockType
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
E.
eraOfQuarrying
Indicates the historical time period during which quarrying activity took place at a given site or for a given material.
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f658a91ba0819084fbe3dd8a09f7cd |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f657f2c8b08190bfeb3173ef78207d |
completed | May 2, 2026, 8 p.m. |
Created at: April 27, 2026, 4:04 a.m.