Triple
T31341838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strečno Castle |
E799325
|
entity |
| Predicate | partiallyReconstructed |
P124228
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Strečno Castle, partiallyReconstructed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyReconstructed Context triple: [Strečno Castle, partiallyReconstructed, true]
-
A.
partlyRebuilt
chosen
Indicates that an entity has been reconstructed or restored to some extent, but not fully.
-
B.
partiallyRestored
Indicates that an entity has been brought back toward a previous or original state, but the restoration is incomplete or only partially achieved.
-
C.
partiallyPreserved
Indicates that the referenced entity or object is only incompletely intact, with some parts missing, damaged, or lost while others remain.
-
D.
restoredInPart
Indicates that something has been brought back to a previous or improved state, but only partially rather than fully.
-
E.
reconstructedAsPartOf
Indicates that one entity has been rebuilt, restored, or recreated as a component or segment of another, larger whole.
- 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 29, 2026, 9:17 p.m.