Triple
T24991610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biot–Savart law |
E625462
|
entity |
| Predicate | givesDirectionBy |
P107429
|
FINISHED |
| Object | right-hand rule |
—
|
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: right-hand rule | Statement: [Biot–Savart law, givesDirectionBy, right-hand rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: givesDirectionBy Context triple: [Biot–Savart law, givesDirectionBy, right-hand rule]
-
A.
locationDirection
Indicates that one entity is located in a specific directional relation (such as north, south, above, or below) relative to another entity.
-
B.
directionBy
chosen
Indicates that one entity provides directional guidance, orientation, or navigational reference for another entity.
-
C.
routeDirectionB
Indicates that one entity represents the direction or orientation of a route or path relative to another entity.
-
D.
geographicDirectionImpliedByName
Indicates that the name of a place or feature suggests a specific geographic direction (e.g., north, south, east, west) relative to some reference.
-
E.
canProvideDirections
Indicates that one entity is able to give another entity guidance or instructions on how to reach a particular location or navigate a route.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 6:03 a.m.