Triple
T30961925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheltenham Roar |
E788849
|
entity |
| Predicate | audibleFeature |
P48651
|
FINISHED |
| Object | collective shout |
—
|
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: collective shout | Statement: [Cheltenham Roar, audibleFeature, collective shout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audibleFeature Context triple: [Cheltenham Roar, audibleFeature, collective shout]
-
A.
audibleIn
Indicates that a sound produced by one entity can be heard within the spatial or contextual range of another entity.
-
B.
hasAudiobookVersion
Indicates that an entity has a corresponding version available in audiobook format.
-
C.
hasAudioFeature
chosen
Indicates that one entity possesses or is associated with a specific audio-related characteristic or property.
-
D.
readingFeature
Indicates that an entity possesses a characteristic, capability, or attribute specifically related to reading.
-
E.
audioOnlyFeatureIntroduced
Indicates that a feature has been introduced which supports or enables audio-only functionality, without accompanying visual content.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:54 p.m.