Triple
T25142236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Slufter |
E629832
|
entity |
| Predicate | hasOpenConnectionTo |
P8776
|
FINISHED |
| Object | North Sea |
E2599
|
NE 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: North Sea | Statement: [De Slufter, hasOpenConnectionTo, North Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpenConnectionTo Context triple: [De Slufter, hasOpenConnectionTo, North Sea]
-
A.
hasConnection
chosen
Indicates that there exists a link, association, or relationship between two entities.
-
B.
openedInConnectionWith
Indicates that one entity was opened as a direct result of, or in association with, another specific event, action, or entity.
-
C.
hasAccessibleConnection
Indicates that there exists a way for one entity to reach or interact with another in a manner that meets defined accessibility requirements.
-
D.
hasLocalConnections
Indicates that an entity maintains relationships, ties, or affiliations within a specific local area or community.
-
E.
hasModeConnection
Indicates a relationship where one entity is linked to another through a specific mode, method, or type of connection.
- F. None of above.
Provenance (4 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1067bd00a88190b6c599c6ebc9044e |
completed | May 22, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 6:29 a.m.