Triple
T458534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caribana |
E7283
|
entity |
| Predicate | hasAudienceSize |
P15029
|
FINISHED |
| Object | over one million attendees per year |
—
|
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: over one million attendees per year | Statement: [Caribana, hasAudienceSize, over one million attendees per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAudienceSize Context triple: [Caribana, hasAudienceSize, over one million attendees per year]
-
A.
hasAudience
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
-
B.
approximateAudienceSize
Indicates an estimated number of individuals or entities that are expected to be reached or affected in a given context.
-
C.
audienceSizeApproximate
Indicates an estimated or approximate number of people in the audience for an event or content.
-
D.
hasTypicalFirstCohortSize
Indicates the usual or standard number of individuals in the first cohort associated with an entity.
-
E.
hasCurrentNumberOfMembers
Indicates the current count of members associated with a given entity.
- F. None of above. chosen
Provenance (4 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efa3163081909acff040a22bd559 |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede75b6c81908350103d21f22a03 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef257a548190a96bfa0cf6183976 |
completed | Feb. 28, 2026, 1:35 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.