Triple
T17643204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ležáky |
E429289
|
entity |
| Predicate | buildings |
P128371
|
FINISHED |
| Object | all original houses destroyed |
—
|
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: all original houses destroyed | Statement: [Ležáky, buildings, all original houses destroyed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildings Context triple: [Ležáky, buildings, all original houses destroyed]
-
A.
building
Indicates that one entity constructs, assembles, or develops another entity, typically over a period of time.
-
B.
publicBuilding
Indicates that a building is designated for public use or access, typically serving communal, governmental, or civic functions.
-
C.
buildingStructure
Indicates that one entity is a structural component or physical part that forms, supports, or constitutes the construction of another entity.
-
D.
buildingComplex
Indicates a relationship where multiple buildings are grouped and function together as a single integrated complex.
-
E.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46de7055c819080d315bb3637882b |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 6:03 a.m.