Triple

T21763347
Position Surface form Disambiguated ID Type / Status
Subject Max-E3-LIN-2 E537215 entity
Predicate isUniformVariant P145853 FINISHED
Object each constraint has exactly 3 variables 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: each constraint has exactly 3 variables | Statement: [Max-E3-LIN-2, isUniformVariant, each constraint has exactly 3 variables]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isUniformVariant
Context triple: [Max-E3-LIN-2, isUniformVariant, each constraint has exactly 3 variables]
  • A. usesUniform
    Indicates that one entity regularly wears or employs a standardized set of clothing or equipment designated as a uniform.
  • B. includesUniformType
    Indicates that one entity contains or encompasses a specific type of uniform within its scope or composition.
  • C. requiresUniformity
    Indicates that one entity imposes a condition that another entity (or set of entities) must be consistent or identical in a specified aspect.
  • D. hasVariant
    Indicates that one entity exists as an alternative form, version, or variation of another entity.
  • E. isNonUniform
    Indicates that the property, distribution, or structure of something varies across its domain rather than remaining constant or uniform.
  • 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.