Triple
T6833413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gauss |
E157391
|
entity |
| Predicate | isUsedToMeasure |
P39778
|
FINISHED |
| Object | strength of magnetic fields |
—
|
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: strength of magnetic fields | Statement: [gauss, isUsedToMeasure, strength of magnetic fields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedToMeasure Context triple: [gauss, isUsedToMeasure, strength of magnetic fields]
-
A.
designedToMeasure
Indicates that one entity was intentionally created or configured for the purpose of quantifying, assessing, or evaluating another entity or its properties.
-
B.
typeOfMeasure
Indicates that one entity specifies the kind or category of measurement used to quantify or evaluate another entity.
-
C.
hasMeasurement
Indicates that an entity is associated with a specific measured value, often including a unit or measurement context.
-
D.
measuredAs
chosen
Indicates that one entity’s quantity, value, or property is expressed or recorded using another entity as its measurement or unit.
-
E.
measuredBy
Indicates that something’s quantity, extent, or value is determined or expressed using a particular measurement method, instrument, or unit.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d62b1e8c8190a81d91191a54b073 |
completed | March 27, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.