Triple
T19050246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anime Expo |
E466237
|
entity |
| Predicate | approximateAttendanceCategory |
P57039
|
FINISHED |
| Object | tens of thousands |
—
|
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: tens of thousands | Statement: [Anime Expo, approximateAttendanceCategory, tens of thousands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateAttendanceCategory Context triple: [Anime Expo, approximateAttendanceCategory, tens of thousands]
-
A.
averageAttendanceCategory
chosen
Indicates the attendance range or classification into which an entity’s typical or mean attendance level falls.
-
B.
hasApproximateNumberOfPeople
Indicates that an entity is associated with an estimated or approximate count of people, rather than an exact number.
-
C.
approximateAudienceSize
Indicates an estimated number of individuals or entities that are expected to be reached or affected in a given context.
-
D.
estimatedCumulativeAttendance
Indicates the total number of attendees expected to have been present over a period of time, aggregated up to a given point.
-
E.
audienceSizeApproximate
Indicates an estimated or approximate number of people in the audience for an event or content.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc018d8c819080525ad104a85fe2 |
completed | April 20, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.