Triple

T32043790
Position Surface form Disambiguated ID Type / Status
Subject Milne universe model E818283 entity
Predicate hasScaleFactor P14260 FINISHED
Object a(t) ∝ t 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: a(t) ∝ t | Statement: [Milne universe model, hasScaleFactor, a(t) ∝ t]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasScaleFactor
Context triple: [Milne universe model, hasScaleFactor, a(t) ∝ t]
  • A. hasScaleFactorForm chosen
    Indicates that one entity is represented as a scaled version or proportional form of another, typically via a specific scale factor.
  • B. hasScale
    Indicates that one entity possesses or is characterized by a scale or graduated measurement system related to another entity.
  • C. hasScaleSize
    Indicates that one entity possesses a scale characterized by a particular size or magnitude in relation to another entity or value.
  • D. hasScaleHeight
    Indicates the characteristic vertical distance over which a quantity (such as pressure, density, or concentration) decreases by a fixed factor in a stratified medium.
  • E. hasScaleParameter
    Indicates that an entity is associated with a scale parameter that controls the magnitude or dispersion of a related quantity or distribution.
  • 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_69f348fcfb648190859f6be5e04b7cfe completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fbad1e94988190b86d447a68e65067 completed May 6, 2026, 9:05 p.m.
PD Predicate disambiguation batch_69fba881b8e0819094790935152b99a1 completed May 6, 2026, 8:45 p.m.
Created at: May 1, 2026, 12:19 a.m.