Triple
T18395489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Cathedral of St. John of Nepomuk |
E449855
|
entity |
| Predicate | primaryFacadeOrientation |
P20200
|
FINISHED |
| Object | west |
—
|
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: west | Statement: [Roman Catholic Cathedral of St. John of Nepomuk, primaryFacadeOrientation, west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFacadeOrientation Context triple: [Roman Catholic Cathedral of St. John of Nepomuk, primaryFacadeOrientation, west]
-
A.
façadeOrientation
chosen
Indicates the directional orientation that a building’s façade faces relative to a reference (e.g., cardinal directions or a main street).
-
B.
primaryDirection
Indicates the main or dominant directional orientation associated with an entity or relation.
-
C.
entranceOrientation
Indicates the directional orientation or facing direction of an entrance relative to a reference frame or environment.
-
D.
poleOrientation
Indicates the directional alignment or facing of a pole relative to a reference frame or coordinate system.
-
E.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to another entity.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e51846bb4c8190990f42a792a78ee0 |
completed | April 19, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:46 a.m.