Triple
T24616331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olenyok Gulf |
E609270
|
entity |
| Predicate | seaShore |
P26064
|
FINISHED |
| Object | Laptev 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: Laptev Sea | Statement: [Olenyok Gulf, seaShore, Laptev Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seaShore Context triple: [Olenyok Gulf, seaShore, Laptev Sea]
-
A.
shore
chosen
Indicates a relationship where one entity forms or lies along the edge or boundary of a body of water, such as a sea, lake, or river.
-
B.
shoreType
Indicates the kind or classification of a shoreline associated with a body of water or coastal area.
-
C.
touchesSea
Indicates that one entity is in direct physical contact with the sea or coastline of another entity.
-
D.
shoreHas
Indicates that a shore possesses, contains, or is characterized by a particular feature, object, or attribute.
-
E.
seaOf
Indicates a relationship where one entity is metaphorically or literally surrounded or filled by another like a vast sea, emphasizing overwhelming abundance or expansiveness.
- 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_69e2c4d1140081909c58667bf68f80c3 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:31 a.m.