Triple
T7133157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East African Coastal Current |
E166239
|
entity |
| Predicate | generalFlowDirection |
P19752
|
FINISHED |
| Object | northward |
—
|
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: northward | Statement: [East African Coastal Current, generalFlowDirection, northward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: generalFlowDirection Context triple: [East African Coastal Current, generalFlowDirection, northward]
-
A.
dataFlowDirection
Indicates the direction in which data moves or is transmitted from a source entity to a target entity.
-
B.
flowsGenerallyDirection
chosen
Indicates that something typically moves or progresses in a particular overall direction, without requiring an exact or constant path.
-
C.
pilgrimFlowDirection
Indicates the direction in which pilgrims move or travel along a route, path, or within a pilgrimage site.
-
D.
circuitDirection
Indicates the orientation or flow direction of a circuit or circuit path relative to its components or layout.
-
E.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with 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_69c68884a9388190af42f90d1c1a7151 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e6703ad88190a498665500fee5a1 |
completed | March 27, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c7289881909f3b533c384f9ed4 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:45 p.m.