Triple
T7132055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dzvina |
E166211
|
entity |
| Predicate | hasHistoricalSignificanceAs |
P4345
|
FINISHED |
| Object | medieval trade route |
—
|
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: medieval trade route | Statement: [Dzvina, hasHistoricalSignificanceAs, medieval trade route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalSignificanceAs Context triple: [Dzvina, hasHistoricalSignificanceAs, medieval trade route]
-
A.
hasHistoricalSignificance
chosen
Indicates that something possesses notable importance or influence within a historical context or period.
-
B.
hasPoliticalSignificanceFor
Indicates that something holds importance, influence, or consequence within the political context or interests of a particular entity.
-
C.
historicalNotability
Indicates that an entity is recognized as having significant importance, influence, or prominence in history.
-
D.
hasMilitarySignificance
Indicates that something holds strategic or tactical importance for military planning, operations, or defense objectives.
-
E.
hasNotableHistoricalAssociation
Indicates that there is a significant connection between an entity and an important historical event, figure, period, or development.
- 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_69c68884a9388190af42f90d1c1a7151 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e66f15b88190bc1fb0f0a8af16a6 |
completed | March 27, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c7289881909f3b533c384f9ed4 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:45 p.m.