Triple

T6396847
Position Surface form Disambiguated ID Type / Status
Subject quantum mechanics E143961 entity
Predicate approximateLimit P4460 FINISHED
Object classical mechanics at macroscopic scales 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: classical mechanics at macroscopic scales | Statement: [quantum mechanics, approximateLimit, classical mechanics at macroscopic scales]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: approximateLimit
Context triple: [quantum mechanics, approximateLimit, classical mechanics at macroscopic scales]
  • A. isLimitOf
    Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
  • B. gLimit
    Indicates a constraint or maximum boundary imposed on the magnitude, rate, or extent of something within a given context.
  • C. approximateCapacity
    Indicates that one entity has an estimated or rough capacity value relative to another or to a specified measure.
  • D. approximates chosen
    Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
  • E. limitaCon
    Indicates that one entity imposes a restriction, constraint, or limit on another entity or its behavior.
  • 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_69c008db906c819096f3597d55d95432 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c068953968819083a94f5de3e11819 completed March 22, 2026, 10:09 p.m.
PD Predicate disambiguation batch_69c060f25c088190b433f78553ff1d84 completed March 22, 2026, 9:36 p.m.
Created at: March 22, 2026, 4:35 p.m.