Triple
T20196965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bullet in a Bible |
E493109
|
entity |
| Predicate | recordedAudienceSize |
P15029
|
FINISHED |
| Object | 65000 |
—
|
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: 65000 | Statement: [Bullet in a Bible, recordedAudienceSize, 65000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordedAudienceSize Context triple: [Bullet in a Bible, recordedAudienceSize, 65000]
-
A.
liveAudiencePresent
Indicates that a live, physically present audience is attending the event or performance.
-
B.
hasAudienceSize
chosen
Indicates the relationship between an entity and the number of people or size of group that receives, views, or engages with it.
-
C.
approximateAudienceSize
Indicates an estimated number of individuals or entities that are expected to be reached or affected in a given context.
-
D.
audienceSizeApproximate
Indicates an estimated or approximate number of people in the audience for an event or content.
-
E.
ticketedAudience
Indicates that the audience for an event or activity is required to obtain tickets (i.e., attendance is controlled or limited via ticketing).
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad99d50819090ddb7b546c65321 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:37 p.m.