Triple
T31943686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V_cs |
E815590
|
entity |
| Predicate | hasMagnitudeUncertaintyApprox |
P52586
|
FINISHED |
| Object | 0.0001–0.0002 |
—
|
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: 0.0001–0.0002 | Statement: [V_cs, hasMagnitudeUncertaintyApprox, 0.0001–0.0002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMagnitudeUncertaintyApprox Context triple: [V_cs, hasMagnitudeUncertaintyApprox, 0.0001–0.0002]
-
A.
hasApproximateValueUncertainty
chosen
Indicates that the value of something is known only approximately and carries an associated degree or range of uncertainty.
-
B.
hasMagnitudeProperty
Indicates that an entity is associated with a quantitative magnitude-related property, such as size, intensity, or amount.
-
C.
hasUncertainty
Indicates that the relationship or value is associated with some level or type of uncertainty rather than being fully definite or precise.
-
D.
valueSIWithUncertainty
Indicates that a numerical value is expressed in SI units along with an associated measure of its uncertainty.
-
E.
relativeStandardUncertainty
Indicates the ratio of a measurement’s standard uncertainty to the measured value, expressing uncertainty relative to the magnitude of the quantity.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a005e8a2f7c819085bfc6f04b866d87 |
completed | May 10, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_6a005de82ef08190a015b385d1d3443c |
completed | May 10, 2026, 10:28 a.m. |
Created at: May 1, 2026, 12:06 a.m.