Triple
T30094806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Putnam County Spelling Bee |
E764832
|
entity |
| Predicate | contestantCharacter |
P82094
|
FINISHED |
| Object | Olive Ostrovsky |
—
|
NE NERFINISHED |
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: Olive Ostrovsky | Statement: [Putnam County Spelling Bee, contestantCharacter, Olive Ostrovsky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contestantCharacter Context triple: [Putnam County Spelling Bee, contestantCharacter, Olive Ostrovsky]
-
A.
featuresContestants
chosen
Indicates that something (such as an event, show, or competition) includes or presents certain individuals as contestants.
-
B.
featuresContestantsFrom
Indicates that something, typically a show or event, includes contestants originating from a specified source or group.
-
C.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
D.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
E.
contestantOn
Indicates that one entity participates as a competitor in a contest, show, or competition associated with another entity.
- 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_69f22474e4288190b5f895fe3974aa92 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 29, 2026, 7:07 p.m.