Triple
T16410199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penmaenmawr |
E398540
|
entity |
| Predicate | quarryStatus |
P48450
|
FINISHED |
| Object | largely disused |
—
|
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: largely disused | Statement: [Penmaenmawr, quarryStatus, largely disused]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: quarryStatus Context triple: [Penmaenmawr, quarryStatus, largely disused]
-
A.
excavationStatus
chosen
Indicates the current state or phase of an excavation activity, such as whether it is planned, in progress, paused, or completed.
-
B.
quarryRegion
Indicates that a specified region is the location where quarrying or extraction activities take place.
-
C.
hasQuarries
Indicates that one entity possesses, contains, or is associated with one or more quarries used for extracting stone or similar materials.
-
D.
quarriedFor
Indicates that a location or source is excavated or mined in order to obtain a particular material or resource.
-
E.
quarriedNear
Indicates that a material or resource was extracted from a quarry located close to a specified place or feature.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328731a408190b38dcab0b7bb65ff |
completed | April 18, 2026, 6:45 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.