Triple
T156529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlie-Gibbs Fracture Zone |
E3192
|
entity |
| Predicate | isTraversedBy |
P416
|
FINISHED |
| Object | ocean currents of the North Atlantic |
—
|
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: ocean currents of the North Atlantic | Statement: [Charlie-Gibbs Fracture Zone, isTraversedBy, ocean currents of the North Atlantic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTraversedBy Context triple: [Charlie-Gibbs Fracture Zone, isTraversedBy, ocean currents of the North Atlantic]
-
A.
visitedBy
Indicates that a location or entity is the destination or target of a visit performed by another entity.
-
B.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
-
C.
hasJunctionWith
Indicates that one entity meets or intersects with another at a shared junction point.
-
D.
hasTrail
Indicates that an entity possesses, includes, or is associated with a trail or pathway.
-
E.
crossedBy
chosen
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a2565ded588190a27319aaa0130b4f |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.