Triple

T1503133
Position Surface form Disambiguated ID Type / Status
Subject MLS Next Pro E33839 entity
Predicate usesSubstitutionRules P6249 FINISHED
Object expanded substitutions for development 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: expanded substitutions for development | Statement: [MLS Next Pro, usesSubstitutionRules, expanded substitutions for development]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesSubstitutionRules
Context triple: [MLS Next Pro, usesSubstitutionRules, expanded substitutions for development]
  • A. usesRulesFrom chosen
    Indicates that one entity applies, follows, or is governed by the rules defined or provided by another entity.
  • B. isRuleGoverned
    Indicates that an entity’s behavior, structure, or operation is determined and constrained by explicit rules or formal regulations.
  • C. compositionRule
    Indicates how multiple elements or components are combined or arranged according to a specific rule or pattern.
  • D. usesAlphabet
    Indicates that one entity employs or is written using the alphabet or writing system associated with another entity.
  • E. usesStandard
    Indicates that one entity adopts, follows, or operates according to a specified standard defined by 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_69a885f352a4819099b24ff15489dede completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a90584b8b881908e112c7e59163812 completed March 5, 2026, 4:24 a.m.
PD Predicate disambiguation batch_69a88727ce48819089b482cdc25453d1 completed March 4, 2026, 7:25 p.m.
Created at: March 4, 2026, 7:24 p.m.