Triple
T23419656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kent State Golden Flashes wrestling program |
E560613
|
entity |
| Predicate | hasRostersFor |
P152185
|
FINISHED |
| Object | multiple weight classes |
—
|
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: multiple weight classes | Statement: [Kent State Golden Flashes wrestling program, hasRostersFor, multiple weight classes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRostersFor Context triple: [Kent State Golden Flashes wrestling program, hasRostersFor, multiple weight classes]
-
A.
hasExpandedRoster
Indicates that an entity’s roster, lineup, or membership has increased in size compared to a previous state.
-
B.
activeRostersInclude
Indicates that a specified entity is currently listed as a member within another entity’s active roster.
-
C.
hasTeamFor
Indicates that an entity possesses, is associated with, or is responsible for a specific team designated for a particular purpose or context.
-
D.
rosterBasis
Indicates the underlying criterion or rule used to determine which entities are included on a particular roster.
-
E.
rosterSize
Indicates the total number of individuals included on a given roster.
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a54489d48190b2b2c29701851765 |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:44 p.m.