Triple
T30270754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fréjus Cathedral |
E769786
|
entity |
| Predicate | baptisteryPlan |
P146654
|
FINISHED |
| Object | octagonal |
—
|
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: octagonal | Statement: [Fréjus Cathedral, baptisteryPlan, octagonal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baptisteryPlan Context triple: [Fréjus Cathedral, baptisteryPlan, octagonal]
-
A.
baptisteryArchitecturalStyle
chosen
Indicates the architectural style or design tradition according to which a baptistery is built.
-
B.
hasBaptistery
Indicates that an entity includes, contains, or is associated with a baptistery as part of its structure or facilities.
-
C.
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.
-
D.
cathedralChurch
Indicates that one church serves as the cathedral (principal church and episcopal seat) of another ecclesiastical jurisdiction or entity.
-
E.
baptisteryDating
Indicates the temporal period or date associated with the construction, use, or significance of a baptistery.
- 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_69f224856d9881908c7f0dd64f059672 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f680d43c708190a28635b6f09d3895 |
completed | May 2, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:43 p.m.