Triple
T38577182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winter Equestrian Festival |
E929436
|
entity |
| Predicate | typicalSpectatorsPerSeason |
P82087
|
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: [Winter Equestrian Festival, typicalSpectatorsPerSeason, tens of thousands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSpectatorsPerSeason Context triple: [Winter Equestrian Festival, typicalSpectatorsPerSeason, tens of thousands]
-
A.
typicalVisitorsPerSeason
chosen
Indicates the usual number of visitors associated with each season for a given entity or location.
-
B.
fanAttendance
Indicates the number or presence of fans attending an event, such as a game, show, or performance.
-
C.
hasSpectators
Indicates that an event, activity, or occurrence is being watched or attended by one or more spectators.
-
D.
spectatorInterest
Indicates that one entity has an interest in observing, watching, or following another entity or event as a spectator.
-
E.
spectatorsFrom
Indicates that one or more spectators originate from, are associated with, or come to an event from a particular place or source.
- 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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.