Triple
T28991388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uralkali |
E736032
|
entity |
| Predicate | hasMainPortTerminal |
P942
|
FINISHED |
| Object | Port of St. Petersburg |
—
|
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: Port of St. Petersburg | Statement: [Uralkali, hasMainPortTerminal, Port of St. Petersburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainPortTerminal Context triple: [Uralkali, hasMainPortTerminal, Port of St. Petersburg]
-
A.
hasMajorPort
chosen
Indicates that a location possesses a primary, significant seaport used for major commercial or transportation activities.
-
B.
hasPortAndTerminalActivity
Indicates that an entity engages in operations or activities related to ports and their associated terminals.
-
C.
hasMainPortal
Indicates that one entity serves as the primary or main portal (entry point or access interface) for another entity.
-
D.
hasPortOn
Indicates that one entity possesses or is located adjacent to a port situated on another specified geographic or infrastructural feature (such as a coast, river, or lake).
-
E.
hasPortConnection
Indicates that one entity is linked to another via a port or interface through which data, power, or signals can be transmitted.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69feff70fbec8190b1ff5f943f29613e |
completed | May 9, 2026, 9:33 a.m. |
| PD | Predicate disambiguation | batch_69fefbcd5b7881909cfe52b32f8a4301 |
completed | May 9, 2026, 9:18 a.m. |
Created at: April 28, 2026, 9:26 a.m.