Triple

T31690846
Position Surface form Disambiguated ID Type / Status
Subject Modified Newtonian Dynamics E808785 entity
Predicate hasApproximateValueFor_a0 P9773 FINISHED
Object 1.2e-10 m/s^2 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: 1.2e-10 m/s^2 | Statement: [Modified Newtonian Dynamics, hasApproximateValueFor_a0, 1.2e-10 m/s^2]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasApproximateValueFor_a0
Context triple: [Modified Newtonian Dynamics, hasApproximateValueFor_a0, 1.2e-10 m/s^2]
  • A. hasApproximateValue chosen
    Indicates that one entity’s value is close to, but not exactly equal to, the value of another entity within an acceptable margin of error.
  • B. hasApproximateValueInEnergy
    Indicates that one entity has an estimated or approximate value expressed in terms of energy associated with another entity.
  • C. hasApproximateValueUncertainty
    Indicates that the value of something is known only approximately and carries an associated degree or range of uncertainty.
  • D. representsApproximately
    Indicates that one entity serves as an inexact or close-but-not-exact representation or value of another entity.
  • E. hasApproximateGauge
    Indicates that one entity has a gauge or measurement that is only approximate, not exact, with respect to another entity or reference.
  • 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_69f348ddcbc48190950cabcc25ff29b3 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69fbc9d1dba881908c399b8e1dc13ce2 completed May 6, 2026, 11:08 p.m.
PD Predicate disambiguation batch_69fbc8ec03ac8190a757563f96fab283 completed May 6, 2026, 11:04 p.m.
Created at: April 30, 2026, 11:08 p.m.