Triple

T4402425
Position Surface form Disambiguated ID Type / Status
Subject G.711 E93646 entity
Predicate mosScore P15617 FINISHED
Object around 4.1 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: around 4.1 | Statement: [G.711, mosScore, around 4.1]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mosScore
Context triple: [G.711, mosScore, around 4.1]
  • A. isScoreFor chosen
    Indicates that one value represents the score or result associated with a particular entity, event, or performance.
  • B. scoring
    Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
  • C. scoringUnit
    Indicates that one entity functions as a unit or component responsible for scoring or assigning scores to another entity.
  • D. musicElement
    Indicates a relationship where something functions as a component or structural unit within a piece of music or musical composition.
  • E. mint
    Indicates the act of creating or issuing something new, typically in an official or authoritative capacity (such as producing new currency or tokens).
  • 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_69b345158c748190a2c040fce2da9980 completed March 12, 2026, 10:58 p.m.
NER Named-entity recognition batch_69b352d08a0c8190ac6c125df40eca75 completed March 12, 2026, 11:57 p.m.
PD Predicate disambiguation batch_69b34f597998819092477efdedb51427 completed March 12, 2026, 11:42 p.m.
Created at: March 12, 2026, 11:28 p.m.