Triple
T4953896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euripus Strait |
E111233
|
entity |
| Predicate | hasCurrentDirectionChanges |
P16424
|
FINISHED |
| Object | up to 7–12 times per day |
—
|
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: up to 7–12 times per day | Statement: [Euripus Strait, hasCurrentDirectionChanges, up to 7–12 times per day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrentDirectionChanges Context triple: [Euripus Strait, hasCurrentDirectionChanges, up to 7–12 times per day]
-
A.
hasDirectionVariability
chosen
Indicates that the direction associated with an entity or process is not fixed but varies over time, space, or conditions.
-
B.
hasDirectionType
Indicates that something possesses or is associated with a specific type or category of direction.
-
C.
hasTrafficDirection
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
D.
hasTwoOperationalDirections
Indicates that an entity supports or functions in two distinct operational directions or modes.
-
E.
hasCountingDirection
Indicates the direction or order in which counting or enumeration proceeds between related entities.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71b82dd88190adfb08c3b3191fe0 |
completed | March 20, 2026, 4:11 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3aa1388190b3e0c8ee1ba1e4fa |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:31 p.m.