Triple
T1264922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gloucester Cathedral |
E12578
|
entity |
| Predicate | majorRebuildingPeriod |
P16794
|
FINISHED |
| Object | 14th 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: 14th century | Statement: [Gloucester Cathedral, majorRebuildingPeriod, 14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorRebuildingPeriod Context triple: [Gloucester Cathedral, majorRebuildingPeriod, 14th century]
-
A.
largelyRebuilt
Indicates that an entity has been substantially reconstructed or renovated, with most of its original structure replaced or significantly altered.
-
B.
majorRebuildCompleted
Indicates that a significant reconstruction or overhaul of an entity has been fully completed.
-
C.
eraOfMajorConstruction
Indicates the time period during which the primary or most significant phase of construction for an entity took place.
-
D.
reorganizationPeriod
Indicates the time span during which a structural or organizational change is planned, underway, or in effect.
-
E.
reconstructionPeriod
chosen
Indicates a time span during which something that was damaged, destroyed, or altered is being rebuilt, restored, or substantially repaired.
- 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4c03573a48190b5851f0a734c2d6f |
completed | March 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69a4bb7058e88190825b0cba5ee60b51 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:50 p.m.