Triple
T31141540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vistula River bank |
E793798
|
entity |
| Predicate | historicallyLinedWith |
P16345
|
FINISHED |
| Object | fortified cities |
—
|
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: fortified cities | Statement: [Vistula River bank, historicallyLinedWith, fortified cities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyLinedWith Context triple: [Vistula River bank, historicallyLinedWith, fortified cities]
-
A.
lineHistorically
Indicates that a line or route has existed or operated during a specific historical period or context.
-
B.
historicallyLinked
chosen
Indicates that two entities are connected through a shared or related historical event, period, or development.
-
C.
lineHistoricallyPartOf
Indicates that a given line (such as a route, boundary, or infrastructure segment) was formerly included within or belonged to a larger line or system at some point in the past.
-
D.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
-
E.
historicallyExtendedBy
Indicates that something has been continued, expanded, or carried forward over time by another, later entity 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
Created at: April 29, 2026, 9:05 p.m.