Triple
T37537053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aral, Kazakhstan |
E933226
|
entity |
| Predicate | wasPortOn |
P166430
|
FINISHED |
| Object | Aral 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: Aral Sea | Statement: [Aral, Kazakhstan, wasPortOn, Aral Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasPortOn Context triple: [Aral, Kazakhstan, wasPortOn, Aral Sea]
-
A.
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).
-
B.
usedOnPort
Indicates that something is applied, connected, or operates specifically on a given port.
-
C.
hadPortsAt
chosen
Indicates that an entity possessed or maintained ports or harbor facilities at a specified location.
-
D.
port
Indicates a relationship where one entity serves as a harbor, access point, or interface through which another entity can enter, exit, or connect.
-
E.
isPortFor
Indicates that one entity serves as a port, interface, or connection point for another entity.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.