Triple
T15197264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of St Mary and All Saints, Chesterfield |
E363167
|
entity |
| Predicate | hasSpireTwist |
P117085
|
FINISHED |
| Object | clockwise |
—
|
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: clockwise | Statement: [Church of St Mary and All Saints, Chesterfield, hasSpireTwist, clockwise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpireTwist Context triple: [Church of St Mary and All Saints, Chesterfield, hasSpireTwist, clockwise]
-
A.
hasSpireMaterial
Indicates that the material composition of a spire is a specified substance or material.
-
B.
hasTwist
Indicates that an entity (such as a story, object, or feature) includes an unexpected change, reversal, or surprising element relative to what was previously established or anticipated.
-
C.
hasSpireCount
Indicates the number of spires that an entity possesses or features.
-
D.
hasTalons
Indicates that an entity possesses talons as a physical feature.
-
E.
hasHeroPower
Indicates that one entity possesses or is endowed with a special ability or power characteristic of a hero in relation to another entity.
- F. None of above. chosen
Provenance (4 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0067fcc788190abdc083d4eadeb36 |
completed | April 15, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec72059c08190a34f513a00185b08 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:10 a.m.