Triple
T29427189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frýdek Castle |
E746326
|
entity |
| Predicate | laterRebuiltIn |
P529
|
FINISHED |
| Object | Renaissance period |
—
|
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: Renaissance period | Statement: [Frýdek Castle, laterRebuiltIn, Renaissance period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRebuiltIn Context triple: [Frýdek Castle, laterRebuiltIn, Renaissance period]
-
A.
laterRebuiltAs
Indicates that one entity was reconstructed or redeveloped at a later time to become or be replaced by another specific entity.
-
B.
notRebuiltAfter
Indicates that an entity was destroyed or damaged and has not been reconstructed or restored after a specified event or point in time.
-
C.
reconstructedAfter
chosen
Indicates that one entity has been rebuilt, restored, or reassembled following the occurrence or existence of another entity or event.
-
D.
rebuiltWith
Indicates that one entity has been reconstructed, restored, or significantly modified using another entity as a material, component, or basis.
-
E.
rebuiltUnder
Indicates that an entity was reconstructed or restored while being subject to the authority, control, or governance of 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
Created at: April 28, 2026, 3:10 p.m.