Triple
T5428771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hallowell granite |
E121431
|
entity |
| Predicate | quarryingBegan |
P22210
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Hallowell granite, quarryingBegan, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: quarryingBegan Context triple: [Hallowell granite, quarryingBegan, 19th century]
-
A.
historicalPeriodOfIntensiveQuarrying
chosen
Indicates the time span during which quarrying activities were especially frequent or intensive for a given site or resource.
-
B.
quarriedFor
Indicates that a location or source is excavated or mined in order to obtain a particular material or resource.
-
C.
quarriedNear
Indicates that a material or resource was extracted from a quarry located close to a specified place or feature.
-
D.
majorExcavationsBegan
Indicates that significant archaeological or construction excavation work was initiated at a particular time or for a particular project.
-
E.
collieryOpened
Indicates that a colliery (coal mine) was opened or began operations.
- 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_69bd463c65f0819082ee6483ab4b466a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8911a7348190ad9378a248190f07 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd846b8bdc81909dcdc2a3084226f2 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:06 p.m.