Triple

T34585681
Position Surface form Disambiguated ID Type / Status
Subject S^2 × R geometry E888036 entity
Predicate localModelFor P181478 FINISHED
Object 3-manifolds locally isometric to S^2 × R 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: 3-manifolds locally isometric to S^2 × R | Statement: [S^2 × R geometry, localModelFor, 3-manifolds locally isometric to S^2 × R]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: localModelFor
Context triple: [S^2 × R geometry, localModelFor, 3-manifolds locally isometric to S^2 × R]
  • A. hasLocalModel
    Indicates that one entity possesses or uses a model that is stored or executed locally rather than accessed remotely.
  • B. localFormOf
    Indicates that one entity is a localized or region-specific version or variant of another, more general entity.
  • C. localFactorAt
    Indicates a relationship where a specific factor or influence is associated with, or applies at, a particular local point, position, or context.
  • D. modelingLocation
    Indicates the place or setting where the modeling activity or process occurs.
  • E. localBehavior
    Indicates that a behavior or effect is determined primarily by nearby or immediate context rather than by distant or global factors.
  • 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_69f349d25cbc8190869998de5915886b completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7764ab1fc81909f9348db87bd7692 completed May 3, 2026, 4:22 p.m.
PD Predicate disambiguation batch_69f76905d9c88190b1ee810bc9ab644f completed May 3, 2026, 3:25 p.m.
PDg Predicate description generation batch_69f77648979c8190b6cdbb835ab8987c completed May 3, 2026, 4:22 p.m.
Created at: May 1, 2026, 2:03 a.m.