Triple

T32738695
Position Surface form Disambiguated ID Type / Status
Subject Hijaz scale E837160 entity
Predicate characterizedByInterval P70298 FINISHED
Object augmented second 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: augmented second | Statement: [Hijaz scale, characterizedByInterval, augmented second]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: characterizedByInterval
Context triple: [Hijaz scale, characterizedByInterval, augmented second]
  • A. hasIntervalStructure
    Indicates that something possesses or is organized according to a specific interval-based structure or pattern.
  • B. invariantInterval
    Indicates that a certain interval or range remains unchanged or constant under a specified transformation or set of conditions.
  • C. characteristicInterval chosen
    Indicates the specific interval or range that most characteristically represents the extent, duration, or variation of a given property or phenomenon.
  • D. typicalExampleInterval
    Indicates the characteristic or most representative time span during which an associated event, state, or condition typically occurs.
  • E. hasInterval
    Indicates that something is associated with a specific span or range between two points in time, space, or value.
  • 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_69f34936e1748190b797e406e4e9293a completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69ff14d596e88190be5263b7f96a96cd completed May 9, 2026, 11:04 a.m.
PD Predicate disambiguation batch_69ff13f0208081909369aeb3b77a6b1f completed May 9, 2026, 11:01 a.m.
Created at: May 1, 2026, 1:12 a.m.