Triple
T2892957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bytča |
E63869
|
entity |
| Predicate | Bytča Castle_notableFeature |
P43825
|
FINISHED |
| Object | wedding palace of the Thurzó family |
—
|
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: wedding palace of the Thurzó family | Statement: [Bytča, Bytča Castle_notableFeature, wedding palace of the Thurzó family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Bytča Castle_notableFeature Context triple: [Bytča, Bytča Castle_notableFeature, wedding palace of the Thurzó family]
-
A.
hasFamousCastle
Indicates that an entity possesses or is the location of a castle that is widely recognized or renowned.
-
B.
castleOverlooks
Indicates that a castle is positioned so that it has a clear, elevated view over a particular area, object, or landscape.
-
C.
hasCastle
Indicates that one entity possesses, controls, or contains a castle.
-
D.
castleBuiltFor
Indicates that a castle was constructed specifically for the benefit, use, or commission of a particular person, group, or purpose.
-
E.
castleLocatedIn
Indicates that a castle is situated within or belongs to a specific geographic or administrative location.
- 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_69ab4c45822c8190830c5f2bb97bcfd0 |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe062234c81909411e34db7d2683d |
completed | March 7, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69abdd17bcdc8190aa47274a50ba4ad4 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde0f4c648190b9812e64f30c39da |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 10:07 p.m.