Triple
T24781067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Лаперу́зов пролив |
E619996
|
entity |
| Predicate | типТечения |
P8232
|
FINISHED |
| Object | сильные приливно-отливные течения |
—
|
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: сильные приливно-отливные течения | Statement: [Лаперу́зов пролив, типТечения, сильные приливно-отливные течения]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: типТечения Context triple: [Лаперу́зов пролив, типТечения, сильные приливно-отливные течения]
-
A.
тип реки
Indicates the classification or category of a river based on its characteristics or role.
-
B.
flowType
chosen
Indicates the kind or category of flow (such as direction, pattern, or mode of movement/transfer) that characterizes the relationship between entities.
-
C.
driftType
Indicates the manner or category of deviation or change from an expected or original state.
-
D.
drainageType
Indicates the kind or classification of drainage associated with or applied to an entity (e.g., how water is removed or flows from it).
-
E.
hasFlowRegime
Indicates that one entity is characterized by, or operates under, a particular pattern or regime of flow.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410d67a208190909034a085b20b59 |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:44 a.m.