Triple
T30656763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bardon Hill |
E780405
|
entity |
| Predicate | operatorOfQuarry |
P200025
|
FINISHED |
| Object | Aggregate Industries |
—
|
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: Aggregate Industries | Statement: [Bardon Hill, operatorOfQuarry, Aggregate Industries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorOfQuarry Context triple: [Bardon Hill, operatorOfQuarry, Aggregate Industries]
-
A.
eraOfQuarrying
Indicates the historical time period during which quarrying activity took place at a given site or for a given material.
-
B.
quarrySource
Indicates that one entity serves as the extraction site or origin location from which another entity (typically a material or resource) is quarried.
-
C.
hasQuarries
Indicates that one entity possesses, contains, or is associated with one or more quarries used for extracting stone or similar materials.
-
D.
hasQuarryType
Indicates that an entity functions as or is associated with a quarry of a specified type.
-
E.
quarriedFor
Indicates that a location or source is excavated or mined in order to obtain a particular material or resource.
- 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_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff6c061c6c81909ff485e9cafc88a2 |
completed | May 9, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ff6aaf886c8190a3c87d089453f3de |
completed | May 9, 2026, 5:11 p.m. |
| PDg | Predicate description generation | batch_69ff6c04fa208190b1fab40a71ef923f |
completed | May 9, 2026, 5:16 p.m. |
Created at: April 29, 2026, 8:30 p.m.