Triple
T37785639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | heliospheric current sheet |
E941946
|
entity |
| Predicate | hasElectricCurrentDirection |
P30562
|
FINISHED |
| Object | azimuthal |
—
|
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: azimuthal | Statement: [heliospheric current sheet, hasElectricCurrentDirection, azimuthal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectricCurrentDirection Context triple: [heliospheric current sheet, hasElectricCurrentDirection, azimuthal]
-
A.
circuitDirection
chosen
Indicates the orientation or flow direction of a circuit or circuit path relative to its components or layout.
-
B.
powerDirection
Indicates the direction in which power, influence, or control flows from one entity to another.
-
C.
electricalPolarity
Indicates that there is a relationship specifying the direction or type of electrical charge or potential difference associated with an entity or connection.
-
D.
hasDirectionOfFlow
Indicates that something moves or is transmitted from one entity or location toward another along a specific path or orientation.
-
E.
electrificationLimitDirection
Indicates the direction or orientation in which an electrification limit (the boundary of an electrified section) applies along a linear infrastructure element such as a track or line.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:19 p.m.