Triple

T7631966
Position Surface form Disambiguated ID Type / Status
Subject Great Ball Court E172777 entity
Predicate hasAcousticPhenomenon P22084 FINISHED
Object whispers can be heard clearly across the court 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: whispers can be heard clearly across the court | Statement: [Great Ball Court, hasAcousticPhenomenon, whispers can be heard clearly across the court]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAcousticPhenomenon
Context triple: [Great Ball Court, hasAcousticPhenomenon, whispers can be heard clearly across the court]
  • A. hasSound chosen
    Indicates that an entity produces, emits, or is associated with a particular sound.
  • B. hasAcousticVersionBy
    Indicates that one entity is an acoustic version of another, created or performed by a specified agent.
  • C. acousticProperty
    Indicates the relationship between an entity and its sound-related characteristics, such as loudness, pitch, timbre, or other acoustic features.
  • D. hasAudioFeature
    Indicates that one entity possesses or is associated with a specific audio-related characteristic or property.
  • E. hasHeavierSoundThan
    Indicates that one entity produces or is associated with a sound that is sonically heavier, more intense, or more forceful than that of another entity.
  • 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_69c69952849881908fdcea7a93bfc307 completed March 27, 2026, 2:50 p.m.
NER Named-entity recognition batch_69c6faa4d2808190942129110711788b completed March 27, 2026, 9:46 p.m.
PD Predicate disambiguation batch_69c6f4e8cadc8190b7977fcd213954dd completed March 27, 2026, 9:21 p.m.
Created at: March 27, 2026, 3:57 p.m.