Triple
T29809021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live Earth |
E756907
|
entity |
| Predicate | hadGlobalAudienceEstimate |
P3653
|
FINISHED |
| Object | 2,000,000,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: 2,000,000,000 | Statement: [Live Earth, hadGlobalAudienceEstimate, 2,000,000,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadGlobalAudienceEstimate Context triple: [Live Earth, hadGlobalAudienceEstimate, 2,000,000,000]
-
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.
viewershipEstimateUnit
Indicates the unit of measurement used to express a viewership estimate (e.g., viewers, households, percentage).
-
D.
hasApproximateNumberOfPeople
Indicates that an entity is associated with an estimated or approximate count of people, rather than an exact number.
-
E.
hasAudienceReach
Indicates the extent or scope of people or groups that are exposed to, can access, or are targeted by a particular entity, message, or activity.
- 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_69f2245584848190ad4cab1f07752ccb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6752cfa9481909ae0dbd7fbf8e3eb |
completed | May 2, 2026, 10:05 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:22 p.m.