Triple
T1894802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The 25th Annual Putnam County Spelling Bee |
E41953
|
entity |
| Predicate | includesAudienceParticipation |
P25673
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The 25th Annual Putnam County Spelling Bee, includesAudienceParticipation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesAudienceParticipation Context triple: [The 25th Annual Putnam County Spelling Bee, includesAudienceParticipation, true]
-
A.
hasAudienceReception
Indicates the relationship between a work or event and how it is received, perceived, or evaluated by its audience.
-
B.
hasAudience
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
-
C.
invitesParticipationOf
chosen
Indicates that one entity actively requests or encourages another entity to take part in an activity, event, or process.
-
D.
participation
Indicates that an entity takes part in, contributes to, or is involved in a shared activity, event, or process with others.
-
E.
participationModel
Indicates how entities are involved in or contribute to an activity, process, or interaction.
- 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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb16c09e48190a345c95eab59fd87 |
completed | March 7, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69abafe7e7e88190b58c0df59187c0c2 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.