Triple
T26645203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isthmus of Kra region |
E668887
|
entity |
| Predicate | oceanBasinWest |
P2049
|
FINISHED |
| Object | eastern Indian Ocean |
—
|
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: eastern Indian Ocean | Statement: [Isthmus of Kra region, oceanBasinWest, eastern Indian Ocean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oceanBasinWest Context triple: [Isthmus of Kra region, oceanBasinWest, eastern Indian Ocean]
-
A.
oceanBasin
chosen
Indicates a relationship where a geographic or marine feature is located within, or is part of, a specific ocean basin.
-
B.
locatedInSeaBasin
Indicates that something is situated within or belongs to a particular sea basin.
-
C.
oceanicPortion
Indicates that one entity is a part or segment of an ocean or oceanic area in relation to another entity.
-
D.
majorOcean
Indicates that one entity is the primary or most significant ocean associated with the other entity.
-
E.
oceanBasinCode
Indicates the standardized code that identifies the ocean basin associated with an entity or location.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61634abb48190919b74ef5778988a |
completed | May 2, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:31 a.m.