Triple
T38467563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Prague |
E912613
|
entity |
| Predicate | architecturalDevelopment |
P169172
|
FINISHED |
| Object | Romanesque architecture in Prague |
—
|
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: Romanesque architecture in Prague | Statement: [History of Prague, architecturalDevelopment, Romanesque architecture in Prague]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architecturalDevelopment Context triple: [History of Prague, architecturalDevelopment, Romanesque architecture in Prague]
-
A.
architecturalProject
Indicates that one entity is an architectural project associated with, created by, or undertaken for another entity.
-
B.
hasArchitecturalDevelopment
Indicates that one entity is responsible for or associated with the architectural development or design of another entity.
-
C.
architecturalPlanner
Indicates a relationship where an entity is responsible for designing, organizing, or planning the architectural structure or layout of another entity.
-
D.
architecturalWork
Indicates that one entity is an architectural creation (such as a building or structure) designed or realized by another entity.
-
E.
toArchitecture
chosen
Indicates a relationship in which something is designed, structured, or organized according to a particular architectural style, plan, or system.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: May 3, 2026, 4:31 p.m.