Triple
T25403852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town Hall Tower (Znojmo) |
E636497
|
entity |
| Predicate | hasStyleDetail |
P106662
|
FINISHED |
| Object | Gothic spire |
—
|
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 spire | Statement: [Town Hall Tower (Znojmo), hasStyleDetail, Gothic spire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStyleDetail Context triple: [Town Hall Tower (Znojmo), hasStyleDetail, Gothic spire]
-
A.
hasStyle
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
-
B.
styleDetail
chosen
Indicates a relationship where specific stylistic characteristics or attributes of something are described or specified in detail.
-
C.
hasSubstyle
Indicates that one style is a more specific or subordinate variant of another style within a hierarchical style structure.
-
D.
hasStyleCharacteristics
Indicates that one entity exhibits or embodies the stylistic features, traits, or qualities associated with another entity.
-
E.
hasPowerStyle
Indicates that one entity possesses or exhibits a particular style or manner of using power in relation to another entity or context.
- 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_69e75db361d881908d8701c856da6413 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 21, 2026, 1:52 p.m.