Triple
T16210733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Heritage Institute |
E393455
|
entity |
| Predicate | typeOfMonumentsManaged |
P50756
|
FINISHED |
| Object | castles in the Czech Republic |
—
|
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: castles in the Czech Republic | Statement: [National Heritage Institute, typeOfMonumentsManaged, castles in the Czech Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfMonumentsManaged Context triple: [National Heritage Institute, typeOfMonumentsManaged, castles in the Czech Republic]
-
A.
hasNumberOfMonuments
Indicates the specific count of monuments associated with or present in a given entity.
-
B.
monumentType
Indicates the specific kind or category of monument that an entity is classified as.
-
C.
monumentGroup
chosen
Indicates that one monument belongs to, or is categorized within, a specific group or collection of monuments.
-
D.
builtMonument
Indicates that one entity constructed or created a monument in honor of, or related to, another entity.
-
E.
majorInscriptionSite
Indicates that a location serves as a primary or significant site where inscriptions are prominently found or produced.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e22713282481909c7c0d0782213461 |
completed | April 17, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.