Triple
T9679918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Music of the Spheres World Tour |
E234252
|
entity |
| Predicate | targetAudienceSize |
P3653
|
FINISHED |
| Object | stadium-scale 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: stadium-scale audiences | Statement: [Music of the Spheres World Tour, targetAudienceSize, stadium-scale audiences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetAudienceSize Context triple: [Music of the Spheres World Tour, targetAudienceSize, stadium-scale audiences]
-
A.
approximateAudienceSize
Indicates an estimated number of individuals or entities that are expected to be reached or affected in a given context.
-
B.
audienceSizeApproximate
chosen
Indicates an estimated or approximate number of people in the audience for an event or content.
-
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.
supportsAudienceSize
Indicates that one entity is capable of accommodating or handling an audience of a specified size.
-
E.
estimatedMemberCount
Indicates the approximate or predicted number of members associated with an 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_69ca84c99e34819092e5563a7106cfca |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9c9dcbe881908ae926a5b5eae759 |
completed | April 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b5d40c8190850ad7a351445f32 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:16 p.m.