Triple
T33246061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beauvais Cathedral |
E851103
|
entity |
| Predicate | transeptConstruction |
P198528
|
FINISHED |
| Object | 16th 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: 16th century | Statement: [Beauvais Cathedral, transeptConstruction, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transeptConstruction Context triple: [Beauvais Cathedral, transeptConstruction, 16th century]
-
A.
hasTransept
Indicates that one architectural structure includes or features a transept as part of its design.
-
B.
cathedral
Indicates that an entity is a cathedral, i.e., it has the status or function of a principal church, typically one that is the seat of a bishop.
-
C.
cloisterConstruction
Indicates the construction or building activity specifically related to a cloister or cloistered architectural space.
-
D.
cathedralFeature
Indicates that one entity is a distinctive architectural or structural feature of a cathedral.
-
E.
cathedralChurch
Indicates that one church serves as the cathedral (principal church and episcopal seat) of another ecclesiastical jurisdiction or 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fef112398081909237c3872345968b |
completed | May 9, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69feefb14ec08190ab401987d8c84a23 |
completed | May 9, 2026, 8:26 a.m. |
| PDg | Predicate description generation | batch_69fef1112b0c8190a8eb027edb71e4e0 |
completed | May 9, 2026, 8:32 a.m. |
Created at: May 1, 2026, 1:31 a.m.