Triple
T30577021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagrationovsk |
E778276
|
entity |
| Predicate | hasRailConnectionHistorical |
P19012
|
FINISHED |
| Object | Königsberg |
—
|
NE NERFINISHED |
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: Königsberg | Statement: [Bagrationovsk, hasRailConnectionHistorical, Königsberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailConnectionHistorical Context triple: [Bagrationovsk, hasRailConnectionHistorical, Königsberg]
-
A.
hasRailroadHistoryWith
chosen
Indicates a historical relationship or connection between entities involving railroads, such as shared development, operation, or significant events in railway history.
-
B.
hasRailwayJunctionHistorically
Indicates that an entity historically functioned as a railway junction, where multiple rail lines intersected or connected in the past.
-
C.
hasRailroadHistory
Indicates that an entity is associated with, involved in, or notable for historical events, operations, or developments related to railroads.
-
D.
hasRail
Indicates that something is equipped with, includes, or is connected to a rail or rail system.
-
E.
connectsToRailwayNetwork
Indicates that one entity is physically or functionally linked to a railway network, allowing access or transfer between them.
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 29, 2026, 8:22 p.m.