Triple
T34751590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sokołów Podlaski |
E1001795
|
entity |
| Predicate | gainedRailConnection |
P95666
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Sokołów Podlaski, gainedRailConnection, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainedRailConnection Context triple: [Sokołów Podlaski, gainedRailConnection, late 19th century]
-
A.
connectsToRailwayNetwork
chosen
Indicates that one entity is physically or functionally linked to a railway network, allowing access or transfer between them.
-
B.
hasPassengerRailConnection
Indicates that there exists a passenger rail service linking one location or transport node to another.
-
C.
connectsToRailStation
Indicates that one entity has a direct link, route, or access connection to a rail station.
-
D.
providesRailConnectionsWithin
Indicates that an entity offers or facilitates rail transport links connecting locations inside a specified area or region.
-
E.
hasRail
Indicates that something is equipped with, includes, or is connected to a rail or rail system.
- 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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.