Triple
T2875913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gomel |
E56876
|
entity |
| Predicate | roadTransportHubOf |
P18987
|
FINISHED |
| Object | southeastern Belarus |
—
|
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: southeastern Belarus | Statement: [Gomel, roadTransportHubOf, southeastern Belarus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadTransportHubOf Context triple: [Gomel, roadTransportHubOf, southeastern Belarus]
-
A.
transportationFacility
Indicates that one entity is a facility or location used for the transportation or transit of people or goods in relation to another entity.
-
B.
hasTransportHub
Indicates that a location contains or serves as a central facility where multiple transport routes or modes connect for passenger or cargo movement.
-
C.
transportationJunctionFor
Indicates a location that serves as a connecting point where multiple transportation routes or modes meet, intersect, or transfer.
-
D.
roadNetworkHubOf
chosen
Indicates that one location functions as a central node or hub within the road network relative to another location or area.
-
E.
transportHubType
Indicates the specific category or kind of transport hub associated with an entity (e.g., airport, train station, bus terminal).
- 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abe0061d048190bb1e5a01e7ceb0e2 |
completed | March 7, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:03 p.m.