Triple

T7978606
Position Surface form Disambiguated ID Type / Status
Subject ECMA-372 E185508 entity
Predicate definesNotation P6184 FINISHED
Object ^ (handle to managed object) 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: ^ (handle to managed object) | Statement: [ECMA-372, definesNotation, ^ (handle to managed object)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: definesNotation
Context triple: [ECMA-372, definesNotation, ^ (handle to managed object)]
  • A. notationType
    Indicates the specific system or style of notation used to represent or encode something (such as music, math, or language).
  • B. distinguishingNotation
    Indicates that one entity uses a specific notation or symbol to distinguish or differentiate another entity from similar ones.
  • C. informalNotation
    Indicates that an entity is represented or expressed using a non-standard, simplified, or colloquial form of notation rather than a formal or fully rigorous one.
  • D. notation chosen
    Indicates a conventional way of symbolically representing or writing something, such as concepts, quantities, or operations, within a specific system.
  • E. hasAlternativeNotation
    Indicates that an entity can be represented or written in a different, equivalent form or notation.
  • 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_69ca829851908190b4e03829353ee7c3 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3bf84b1081908e60a556d984aad6 completed March 31, 2026, 3:14 a.m.
PD Predicate disambiguation batch_69cb047a8e4c81909b79e0f0bf56440c completed March 30, 2026, 11:17 p.m.
Created at: March 30, 2026, 5:14 p.m.