Triple
T20120095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bamberg Cathedral |
E490581
|
entity |
| Predicate | groundPlan |
P5930
|
FINISHED |
| Object | basilica with transept |
—
|
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: basilica with transept | Statement: [Bamberg Cathedral, groundPlan, basilica with transept]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groundPlan Context triple: [Bamberg Cathedral, groundPlan, basilica with transept]
-
A.
floorPlan
chosen
Indicates that one entity serves as the architectural layout or room arrangement blueprint for another entity (such as a building or space).
-
B.
plannedArea
Indicates that an area is designated or intended for a specific planned use or development.
-
C.
hasStreetPlan
Indicates that an entity possesses or is associated with a specific layout or design plan for its streets.
-
D.
planning
Indicates that an entity is engaged in organizing or devising a future action, event, or course of behavior involving another entity or entities.
-
E.
floorPlanType
Indicates the specific layout or configuration category that a floor plan belongs to (e.g., studio, 1-bedroom, open-plan).
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6673cfaac81909d6216f3e37c2439 |
completed | April 20, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:30 p.m.