Triple
T17591538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kratovo |
E428459
|
entity |
| Predicate | historicTowerCount |
P5319
|
FINISHED |
| Object | multiple preserved medieval towers |
—
|
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: multiple preserved medieval towers | Statement: [Kratovo, historicTowerCount, multiple preserved medieval towers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicTowerCount Context triple: [Kratovo, historicTowerCount, multiple preserved medieval towers]
-
A.
towerDatingFrom
Indicates that a tower originates from, or was constructed in, a specified time period or date.
-
B.
towerCount
Indicates the number of towers associated with or present in a given entity or context.
-
C.
numberOfTowers
chosen
Indicates the quantity of towers associated with or contained by a given entity.
-
D.
storeysOfTallestTower
Indicates the number of storeys contained in the tallest tower associated with the given context or entity.
-
E.
towerName
Indicates the specific name assigned to a tower in the relationship.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e469e79dac8190953a1ce8fc015b20 |
completed | April 19, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.