Triple
T27567948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Světlá nad Sázavou |
E695952
|
entity |
| Predicate | hasGlassworks |
P163928
|
FINISHED |
| Object | local glass factories |
—
|
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: local glass factories | Statement: [Světlá nad Sázavou, hasGlassworks, local glass factories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGlassworks Context triple: [Světlá nad Sázavou, hasGlassworks, local glass factories]
-
A.
hasStainedGlass
Indicates that one entity possesses or features stained glass as part of its structure or design.
-
B.
hasStainedGlassManufacturer
Indicates that one entity serves as the manufacturer responsible for producing the stained glass associated with another entity.
-
C.
hasGlassArea
Indicates that an object or structure possesses a surface or region made of glass.
-
D.
hasNanoTextureGlassOption
Indicates that an entity offers or includes an available option for nano-texture glass.
-
E.
hasGlassCurtainWall
Indicates that a building or structure features an exterior façade primarily composed of a non-load-bearing glass curtain wall system.
- F. None of above. chosen
Provenance (4 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 1:42 p.m.