Triple
T8954755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariazell Basilica |
E213444
|
entity |
| Predicate | hasNaveStyle |
P60337
|
FINISHED |
| Object | Gothic |
—
|
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: Gothic | Statement: [Mariazell Basilica, hasNaveStyle, Gothic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNaveStyle Context triple: [Mariazell Basilica, hasNaveStyle, Gothic]
-
A.
naveStyle
chosen
Indicates the architectural style or design type applied specifically to the nave portion of a building or structure.
-
B.
hasNave
Indicates that one entity (typically a building or structure) possesses or includes a nave as a distinct architectural part.
-
C.
hasNavePlan
Indicates that an entity possesses or is associated with a specific plan or layout for a nave (the central part of a church or similar building).
-
D.
hasParkStyle
Indicates that an entity possesses or is characterized by a particular style or type of park.
-
E.
hasDomeStyle
Indicates that one entity (typically a building or structure) possesses a dome characterized by a particular architectural style or form.
- 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_69ca8399ad2081909f8fa41d4314c215 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6724f3e4819092c6b13d80871e80 |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7 p.m.