Triple
T17591537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kratovo |
E428459
|
entity |
| Predicate | historicBridgeCount |
P20771
|
FINISHED |
| Object | several preserved stone bridges |
—
|
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: several preserved stone bridges | Statement: [Kratovo, historicBridgeCount, several preserved stone bridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicBridgeCount Context triple: [Kratovo, historicBridgeCount, several preserved stone bridges]
-
A.
isHistoricBridgeOf
Indicates that a bridge has historical significance and serves or served as a notable crossing associated with a particular place or route.
-
B.
hasNumberOfMainBridges
Indicates the quantity of primary or main bridges associated with a given entity.
-
C.
numberOfSwingBridges
Indicates the quantity of swing bridges associated with or present in a given context or entity.
-
D.
coveredBridgeBuilt
Indicates that a covered bridge was constructed or brought into existence.
-
E.
hasNumberOfBridges
chosen
Indicates the quantitative relationship specifying how many bridges are associated with a given 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_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.