Triple
T869008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercury |
E18768
|
entity |
| Predicate | magneticFieldType |
P4541
|
FINISHED |
| Object | global dipolar magnetic field |
—
|
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: global dipolar magnetic field | Statement: [Mercury, magneticFieldType, global dipolar magnetic field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magneticFieldType Context triple: [Mercury, magneticFieldType, global dipolar magnetic field]
-
A.
magneticFieldStrength
Indicates the intensity or magnitude of a magnetic field associated with an entity or at a specific location.
-
B.
fieldType
chosen
Indicates the classification or category that defines the nature or kind of a given field within a structure or context.
-
C.
usesMagnetType
Indicates that one entity employs or operates with a specific type of magnet in its function or configuration.
-
D.
hasMagneticMoment
Indicates that an entity possesses a magnetic moment, characterizing the strength and orientation of its magnetism.
-
E.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac7f98908190883f71049092c7c8 |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa87504481909618a6815948da6f |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.