Triple

T21763278
Position Surface form Disambiguated ID Type / Status
Subject Max-3-SAT E537214 entity
Predicate hasApproximationRatio P145841 FINISHED
Object 7/8 by random assignment 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: 7/8 by random assignment | Statement: [Max-3-SAT, hasApproximationRatio, 7/8 by random assignment]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasApproximationRatio
Context triple: [Max-3-SAT, hasApproximationRatio, 7/8 by random assignment]
  • A. hasApproximateValue
    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. representsApproximately
    Indicates that one entity serves as an inexact or close-but-not-exact representation or value of another entity.
  • C. approximationType
    Indicates the specific method or scheme used to approximate a value, function, or relationship in a given context.
  • D. holdsApproximatelyFor
    Indicates that a condition, relation, or value is valid only to an approximate degree or within a tolerance, rather than holding exactly.
  • E. hasApproximateRate
    Indicates that one entity is associated with another entity representing an estimated or non-exact rate or frequency.
  • F. None of above. chosen

Provenance (4 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_69e0c46f5d1c8190bf830409e98464e5 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f031a711dc8190a786c9849dc344e8 completed April 28, 2026, 4:03 a.m.
PD Predicate disambiguation batch_69e6be6299988190a34c98fa76d94700 completed April 21, 2026, 12:01 a.m.
PDg Predicate description generation batch_69e6d054737081908aa7112975b77475 completed April 21, 2026, 1:18 a.m.
Created at: April 16, 2026, 6:51 p.m.