Triple

T11739900
Position Surface form Disambiguated ID Type / Status
Subject Lambert azimuthal equal-area projection E279123 entity
Predicate canBeDefinedOn P4464 FINISHED
Object 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: sphere | Statement: [Lambert azimuthal equal-area projection, canBeDefinedOn, sphere]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canBeDefinedOn
Context triple: [Lambert azimuthal equal-area projection, canBeDefinedOn, sphere]
  • A. canBeDefinedFor
    Indicates that a certain concept, operation, or property is applicable to and can be meaningfully specified for a given entity or set of entities.
  • B. areDefinedIn
    Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
  • C. definedOn chosen
    Indicates that something (such as a function, rule, or structure) is specified to apply or be valid over a particular domain, set, or context.
  • D. canBeInvokedBy
    Indicates that one entity (such as a function, method, or operation) is able to be called, triggered, or executed by another entity.
  • E. canBeConstructedWith
    Indicates that one entity can be formed, built, or assembled using another entity as material, components, or means.
  • 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_69d6aaffec6881908bead509e8621742 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a4f025f88190a39280806c9d7c33 completed April 10, 2026, 7:21 a.m.
PD Predicate disambiguation batch_69d88a813cc48190a3dfdc60e8af80ae completed April 10, 2026, 5:28 a.m.
Created at: April 8, 2026, 9:41 p.m.