Triple
T30679958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth’s magnetic field |
E781025
|
entity |
| Predicate | hasAverageSurfaceStrength |
P149426
|
FINISHED |
| Object | about 25 to 65 microteslas |
—
|
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: about 25 to 65 microteslas | Statement: [Earth’s magnetic field, hasAverageSurfaceStrength, about 25 to 65 microteslas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAverageSurfaceStrength Context triple: [Earth’s magnetic field, hasAverageSurfaceStrength, about 25 to 65 microteslas]
-
A.
hasAverageSurfaceSpeed
Indicates the typical or mean speed at which something moves across a surface over a given period or distance.
-
B.
hasTypicalStrength
chosen
Indicates that an entity possesses the usual or characteristic level of strength expected for its kind or context.
-
C.
hasApproximateAverageThickness
Indicates that an entity possesses a thickness value that is an estimated or typical average rather than an exact measurement.
-
D.
hasAverageDepth
Indicates that an entity possesses a specified mean depth value, typically measured over its entire extent or area.
-
E.
availableStrength
Indicates the amount of strength or power that an entity currently has ready for use or deployment.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b1b21308190a63dc200654683fc |
completed | May 2, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:32 p.m.