Triple
T11688246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Michael, Cornhill |
E277798
|
entity |
| Predicate | postFireRebuildingPeriod |
P44073
|
FINISHED |
| Object | late 17th 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: late 17th century | Statement: [St Michael, Cornhill, postFireRebuildingPeriod, late 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postFireRebuildingPeriod Context triple: [St Michael, Cornhill, postFireRebuildingPeriod, late 17th century]
-
A.
rebuildPeriod
chosen
Indicates the time span during which something is reconstructed or restored after damage, failure, or decommissioning.
-
B.
rebuiltAfterEvent
Indicates that an entity was reconstructed or restored following a specific event that caused damage, destruction, or significant alteration.
-
C.
rebuiltCompletedIn
Indicates that an entity has undergone a rebuilding process that was fully completed in a specified time or event.
-
D.
patronDuringRebuilding
Indicates that an entity serves as a patron or sponsor of another entity specifically during a rebuilding or reconstruction period.
-
E.
buildPeriodEnd
Indicates the point in time at which a construction or building phase is considered completed.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4654be881909bd0256cf18e25de |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.