Triple
T13654761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | annual Hill Cumorah Pageant |
E326828
|
entity |
| Predicate | typicalAudienceSizePerSeason |
P82087
|
FINISHED |
| Object | 40000 |
—
|
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: 40000 | Statement: [annual Hill Cumorah Pageant, typicalAudienceSizePerSeason, 40000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAudienceSizePerSeason Context triple: [annual Hill Cumorah Pageant, typicalAudienceSizePerSeason, 40000]
-
A.
typicalVisitorsPerSeason
chosen
Indicates the usual number of visitors associated with each season for a given entity or location.
-
B.
audienceSizeApproximate
Indicates an estimated or approximate number of people in the audience for an event or content.
-
C.
approximateAudienceSize
Indicates an estimated number of individuals or entities that are expected to be reached or affected in a given context.
-
D.
hasAudienceSize
Indicates the relationship between an entity and the number of people or size of group that receives, views, or engages with it.
-
E.
typicalSeasonSeriesLength
Indicates the usual number of episodes or installments that make up a single season of a series.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60ace048190a4b92310ba272bd1 |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:52 p.m.