Triple
T32137680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sloviansk |
E820815
|
entity |
| Predicate | isStrategicTransportHub |
P154729
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sloviansk, isStrategicTransportHub, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStrategicTransportHub Context triple: [Sloviansk, isStrategicTransportHub, true]
-
A.
isTransportCenterOf
Indicates that a location functions as a primary hub or central node for transportation activities serving another area or network.
-
B.
isMajorBusHub
Indicates that a location serves as a primary node in the bus network, with high connectivity and significant passenger or route volume.
-
C.
capitalCityIsMajorTransportHub
Indicates that the capital city functions as a primary hub for transportation networks, with significant connectivity and traffic across major transport modes.
-
D.
isKeyTransportHubIn
chosen
Indicates that a location functions as a primary node for transporting people or goods within the specified area or network.
-
E.
isTransportHubType
Indicates that something serves as or belongs to a particular category of transport hub (such as a station, port, or 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9aa7bb4819082571b42370dcd4a |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:30 a.m.