Triple

T26992458
Position Surface form Disambiguated ID Type / Status
Subject SAT E679891 entity
Predicate practicalRelevance P46656 FINISHED
Object used in constraint solving 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: used in constraint solving | Statement: [SAT, practicalRelevance, used in constraint solving]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: practicalRelevance
Context triple: [SAT, practicalRelevance, used in constraint solving]
  • A. actualPractice
    Indicates that an action, method, or behavior is carried out in reality or in day-to-day use, as opposed to being merely theoretical, planned, or prescribed.
  • B. usedInPractice chosen
    Indicates that something is actually applied or implemented in real-world practice rather than just being theoretical or proposed.
  • C. relevantToInstitution
    Indicates that something has a meaningful connection, applicability, or significance to a particular institution.
  • D. publicPractice
    Indicates that an activity, behavior, or belief is carried out openly in public or within a community setting rather than privately.
  • E. influencesPractice
    Indicates that one entity affects, shapes, or alters the way another entity carries out its activities, methods, or customary 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_69eeeb5138ac8190b3c273ddc659a54f completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69f62d53ad58819080c5227c7a729d15 completed May 2, 2026, 4:58 p.m.
PD Predicate disambiguation batch_69f62c15952881908a5ea0c25904afec completed May 2, 2026, 4:53 p.m.
Created at: April 27, 2026, 6:52 a.m.