Triple
T28677726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combe Down quarries |
E725913
|
entity |
| Predicate | stoneProperty |
P16907
|
FINISHED |
| Object | easily worked when freshly quarried |
—
|
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: easily worked when freshly quarried | Statement: [Combe Down quarries, stoneProperty, easily worked when freshly quarried]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stoneProperty Context triple: [Combe Down quarries, stoneProperty, easily worked when freshly quarried]
-
A.
squareProperty
Indicates that one entity is the square (second power) of a numerical property or value associated with another entity.
-
B.
architectureProperty
chosen
Indicates that a specified architectural characteristic or feature is attributed to, or associated with, an entity.
-
C.
lakeProperty
Indicates that a property is located on, adjacent to, or otherwise directly associated with a lake.
-
D.
builtProperty
Indicates that a constructed structure or building has been created on, or is associated with, a particular property or piece of land.
-
E.
basisProperty
Indicates that one property serves as the foundational or defining basis for another property or characteristic.
- 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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6563602d081908925ab65f492fbc2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:07 a.m.