Triple

T3044225
Position Surface form Disambiguated ID Type / Status
Subject Tucker’s lemma E83404 entity
Predicate hasLabelSet P44780 FINISHED
Object {±1,±2,…,±n} in the classical n-dimensional version — 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: {±1,±2,…,±n} in the classical n-dimensional version | Statement: [Tucker’s lemma, hasLabelSet, {±1,±2,…,±n} in the classical n-dimensional version]
PD Predicate disambiguation gpt-5-mini-2025-08-07 
Target predicate: hasLabelSet
Context triple: [Tucker’s lemma, hasLabelSet, {±1,±2,…,±n} in the classical n-dimensional version]
  • A. hasLabel
    Indicates that an entity is associated with a specific textual label or name used to identify or describe it.
  • B. hasStatusLabel
    Indicates that an entity is associated with a specific status expressed as a human-readable label.
  • C. hasDistinctSetFor
    Indicates that one entity is associated with a separate, non-overlapping collection of items or elements specifically designated for another entity.
  • D. canonicalSetIncludes
    Indicates that a canonical or standard set contains the referenced element as one of its members.
  • E. hasMarker
    Indicates that one entity possesses, is associated with, or is identified by a specific marker.
  • 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_69ad8b24924c8190a9bb6f61d519e4ae completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9b5ec5988190b8b6c95c743c6d1e completed March 8, 2026, 3:53 p.m.
PD Predicate disambiguation batch_69ad961fc62c819087c4c3a44b00847d completed March 8, 2026, 3:30 p.m.
PDg Predicate description generation batch_69ad97f6af3881909f4547967384114c completed March 8, 2026, 3:38 p.m.
Created at: March 8, 2026, 3:01 p.m.