Triple

T38260559
Position Surface form Disambiguated ID Type / Status
Subject affine differential geometry E1017916 entity
Predicate hasTypicalObject P76740 FINISHED
Object elliptic affine sphere 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: elliptic affine sphere | Statement: [affine differential geometry, hasTypicalObject, elliptic affine sphere]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTypicalObject
Context triple: [affine differential geometry, hasTypicalObject, elliptic affine sphere]
  • A. typicalObjectType chosen
    Indicates that something is a common or characteristic type of object typically associated with or involved in another entity or situation.
  • B. hasTypicalInstance
    Indicates that a class or category is exemplified by a specific, representative instance that typifies its general characteristics.
  • C. hasTypicalBody
    Indicates that an entity possesses the standard or characteristic physical form commonly associated with its kind or category.
  • D. hasObject
    Indicates that an entity is associated with or possesses a particular object as part of a relationship or action.
  • E. hasTypicalSubject
    Indicates that something is commonly or characteristically used as the subject (agent or topic) of a given relation or action.
  • 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_69f76de33e4481909099fa812709bd42 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_6a00119d821c8190874786391b27ef23 completed May 10, 2026, 5:03 a.m.
PD Predicate disambiguation batch_6a001143fb6881909ac0ae8bfea04351 completed May 10, 2026, 5:01 a.m.
Created at: May 3, 2026, 4:30 p.m.