Triple
T2732717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wild Card round |
E60351
|
entity |
| Predicate | includesSeedRange |
P28992
|
FINISHED |
| Object | wild card seeds and lower division winners |
—
|
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: wild card seeds and lower division winners | Statement: [Wild Card round, includesSeedRange, wild card seeds and lower division winners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesSeedRange Context triple: [Wild Card round, includesSeedRange, wild card seeds and lower division winners]
-
A.
hasSeedCount
Indicates that an entity possesses a specific number of seeds.
-
B.
usesSeeding
Indicates that an entity employs a seeding process or strategy to initiate, distribute, or propagate something (such as data, content, or resources).
-
C.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
D.
rangeOf
chosen
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
E.
seedUse
Indicates the use or application of seeds for a particular purpose, such as planting, cultivation, or propagation.
- 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_69ab4b75cd908190b691ef0d1801acda |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdaf011548190beb9c3feee7b743f |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.