Triple
T264281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midnight Yell Practice |
E5690
|
entity |
| Predicate | audienceSize |
P3846
|
FINISHED |
| Object | tens of thousands for major games |
—
|
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: tens of thousands for major games | Statement: [Midnight Yell Practice, audienceSize, tens of thousands for major games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audienceSize Context triple: [Midnight Yell Practice, audienceSize, tens of thousands for major games]
-
A.
audienceSizeApproximate
Indicates an estimated or approximate number of people in the audience for an event or content.
-
B.
approximateAudienceSize
chosen
Indicates an estimated number of individuals or entities that are expected to be reached or affected in a given context.
-
C.
hasAudience
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
-
D.
hasPopulationApproximate
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
E.
supportedPopulation
Indicates that one entity provides assistance, resources, or services to sustain or benefit a specified group of people.
- 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_69a2587daeb081909591b9d30f80a271 |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25d8e809881908a58c9a4e3ba07c3 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b6e07748190834022a65ba6d803 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:56 a.m.