Triple
T24877102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molotovsk |
E622599
|
entity |
| Predicate | portOn |
P1763
|
FINISHED |
| Object | White Sea |
—
|
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: White Sea | Statement: [Molotovsk, portOn, White Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portOn Context triple: [Molotovsk, portOn, White Sea]
-
A.
port
chosen
Indicates a relationship where one entity serves as a harbor, access point, or interface through which another entity can enter, exit, or connect.
-
B.
portSystem
Indicates that one system serves as a port or interface through which another system connects, communicates, or transfers data or resources.
-
C.
portNumber
Indicates the specific communication port assigned to a network connection, service, or endpoint.
-
D.
portAlsoKnownAs
Indicates that a port is referred to by an alternative name or alias.
-
E.
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).
- 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_69e2fac3fdbc81909c2ec49be5743cd9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:24 a.m.