Triple

T2663847
Position Surface form Disambiguated ID Type / Status
Subject Euler’s polyhedron formula E54784 entity
Predicate usedToCheck P23056 FINISHED
Object combinatorial validity of polyhedral meshes 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: combinatorial validity of polyhedral meshes | Statement: [Euler’s polyhedron formula, usedToCheck, combinatorial validity of polyhedral meshes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedToCheck
Context triple: [Euler’s polyhedron formula, usedToCheck, combinatorial validity of polyhedral meshes]
  • A. usedBefore
    Indicates that one entity was utilized or applied prior to the use or occurrence of another entity.
  • B. isUsedToTest chosen
    Indicates that one entity serves as a means or tool for evaluating, examining, or verifying another entity.
  • C. usedInDetector
    Indicates that something (e.g., a component, material, or method) is employed as part of a detector or detection system.
  • D. usedFor
    Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
  • E. usedToSearchFor
    Indicates that one entity serves as a tool, method, or resource employed to look for, locate, or retrieve another entity.
  • 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_69ab49e028948190b97e01d73548b1d9 completed March 6, 2026, 9:40 p.m.
NER Named-entity recognition batch_69abd96dba44819085c3e651afba7806 completed March 7, 2026, 7:53 a.m.
PD Predicate disambiguation batch_69abd81768748190bd965f367cf6ef37 completed March 7, 2026, 7:47 a.m.
Created at: March 6, 2026, 9:54 p.m.