Triple
T7172678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morro Rock |
E167239
|
entity |
| Predicate | quarryingCeased |
P17533
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Morro Rock, quarryingCeased, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: quarryingCeased Context triple: [Morro Rock, quarryingCeased, 1960s]
-
A.
quarriedNear
Indicates that a material or resource was extracted from a quarry located close to a specified place or feature.
-
B.
quarriedFor
Indicates that a location or source is excavated or mined in order to obtain a particular material or resource.
-
C.
miningActivityEnd
chosen
Indicates the point in time or event at which a mining operation or activity ceases or is formally concluded.
-
D.
quarryingWasImportantFor
Indicates that the activity of quarrying played a significant or central role for the referenced entity, such as in its economy, development, or functioning.
-
E.
historicalPeriodOfIntensiveQuarrying
Indicates the time span during which quarrying activities were especially frequent or intensive for a given site or resource.
- 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_69c68889a2748190a316c5e65360361a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e88b0a448190a19bd2d9e2a310a4 |
completed | March 27, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69c6e1ce5f048190808c378a980f7bb6 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:48 p.m.