Triple
T4396468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collyhurst sandstone |
E99502
|
entity |
| Predicate | historicallyQuarried |
P22210
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Collyhurst sandstone, historicallyQuarried, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyQuarried Context triple: [Collyhurst sandstone, historicallyQuarried, true]
-
A.
quarriedFor
Indicates that a location or source is excavated or mined in order to obtain a particular material or resource.
-
B.
historicalPeriodOfIntensiveQuarrying
chosen
Indicates the time span during which quarrying activities were especially frequent or intensive for a given site or resource.
-
C.
quarriedNear
Indicates that a material or resource was extracted from a quarry located close to a specified place or feature.
-
D.
excavatedFrom
Indicates that something (typically an artifact, fossil, or material) was dug out or uncovered from a specific location or source through excavation.
-
E.
historicallyStoredGoods
Indicates that an entity has previously stored certain goods at some time in the past.
- 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_69b345506b408190b0e3dee616738a7d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352aca86c8190b5af7e6600072066 |
completed | March 12, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69b34f597998819092477efdedb51427 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:20 p.m.