Triple
T2191480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beat of the Future |
E49870
|
entity |
| Predicate | liveAudienceSizeApprox |
P3846
|
FINISHED |
| Object | over 70,000 |
—
|
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: over 70,000 | Statement: [Beat of the Future, liveAudienceSizeApprox, over 70,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liveAudienceSizeApprox Context triple: [Beat of the Future, liveAudienceSizeApprox, over 70,000]
-
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.
hasAudienceSize
Indicates the relationship between an entity and the number of people or size of group that receives, views, or engages with it.
-
D.
audienceCapacityType
Indicates the classification or type of capacity used to describe how many audience members a venue or event space can accommodate.
-
E.
fanAttendance
Indicates the number or presence of fans attending an event, such as a game, show, or performance.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf3f5e008190beda3ce5d77209e0 |
completed | March 7, 2026, 6:01 a.m. |
| PD | Predicate disambiguation | batch_69abbda52328819089c7ab111bebb0ca |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.