Triple
T27517461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Michael and St John’s Church, Great Mitton |
E694610
|
entity |
| Predicate | towerStageCount |
P7615
|
FINISHED |
| Object | three-stage tower |
—
|
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: three-stage tower | Statement: [St Michael and St John’s Church, Great Mitton, towerStageCount, three-stage tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: towerStageCount Context triple: [St Michael and St John’s Church, Great Mitton, towerStageCount, three-stage tower]
-
A.
numberOfStages
chosen
Indicates the total count of distinct stages or phases associated with a given process, event, or entity.
-
B.
numberPerStage
Indicates the quantity or count associated with each distinct stage in a multi-stage process or sequence.
-
C.
stageNumber
Indicates the specific sequential position or order of a stage within a multi-stage process or structure.
-
D.
tierCount
Indicates the number of distinct levels, ranks, or layers associated with an entity in a hierarchical or tiered structure.
-
E.
coreStageLength
Indicates the length or duration of the main or primary stage within a multi-stage process or structure.
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 1:19 p.m.