Triple
T6023172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Bene't's Church, Cambridge |
E134111
|
entity |
| Predicate | towerConstructionPeriod |
P59976
|
FINISHED |
| Object | Anglo-Saxon period |
—
|
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: Anglo-Saxon period | Statement: [St Bene't's Church, Cambridge, towerConstructionPeriod, Anglo-Saxon period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: towerConstructionPeriod Context triple: [St Bene't's Church, Cambridge, towerConstructionPeriod, Anglo-Saxon period]
-
A.
constructionTime
Indicates the duration or specific point in time required to construct or build an entity.
-
B.
towerCompleted
Indicates that the construction of a tower has been fully finished and reached its intended completed state.
-
C.
eraOfMajorConstruction
Indicates the time period during which the primary or most significant phase of construction for an entity took place.
-
D.
towerCompletedBefore
Indicates that the construction or completion of one tower occurred earlier in time than the construction or completion of another tower.
-
E.
towerDatingFrom
chosen
Indicates that a tower originates from, or was constructed in, a specified time period or date.
- 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_69c008742a5c8190b9cb9c2787a3d8b3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04fbd7978819085d683578bc62aa3 |
completed | March 22, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69c049e75b3881908be106fbcf8c68d4 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:07 p.m.