Triple
T20715603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twenty20 cricket |
E509159
|
entity |
| Predicate | spectatorDemographic |
P80245
|
FINISHED |
| Object | family audiences |
—
|
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: family audiences | Statement: [Twenty20 cricket, spectatorDemographic, family audiences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spectatorDemographic Context triple: [Twenty20 cricket, spectatorDemographic, family audiences]
-
A.
hasDemographic
Indicates that an entity is associated with or characterized by a particular demographic group or attribute.
-
B.
audienceComposition
chosen
Indicates the makeup or distribution of different groups or segments within an audience in relation to something.
-
C.
spectatorInterest
Indicates that one entity has an interest in observing, watching, or following another entity or event as a spectator.
-
D.
spectatorType
Indicates the role or category of a spectator in relation to an event or activity.
-
E.
involvesDemographic
Indicates that an action, event, or entity is related to, affects, or includes a specific demographic group or population segment.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1d12a9481909cce3711c1c2d9f8 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:15 p.m.