Triple
T9456331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | oersted |
E228023
|
entity |
| Predicate | physicalQuantityMeasured |
P79330
|
FINISHED |
| Object | magnetic field strength |
—
|
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: magnetic field strength | Statement: [oersted, physicalQuantityMeasured, magnetic field strength]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: physicalQuantityMeasured Context triple: [oersted, physicalQuantityMeasured, magnetic field strength]
-
A.
measuredProperty
Indicates that the subject is a measurement that quantifies or assesses the specified property of an entity.
-
B.
measuredAs
Indicates that one entity’s quantity, value, or property is expressed or recorded using another entity as its measurement or unit.
-
C.
measuredValue
Indicates that a specific quantitative value has been obtained as the result of a measurement of some property or phenomenon.
-
D.
measureType
Indicates the specific kind or category of measurement that characterizes how a quantity or value is assessed.
-
E.
measureOf
chosen
Indicates that one entity serves as a quantitative or qualitative assessment or metric describing a property, extent, or magnitude of 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f8f7e1481909318e473ab4d6460 |
completed | April 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69cca5596ffc819097e9c8eefd4ef9b8 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:52 p.m.