Triple
T37855982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan State Spartans rowing program |
E944190
|
entity |
| Predicate | hasRosters |
P152185
|
FINISHED |
| Object | varsity athletes |
—
|
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: varsity athletes | Statement: [Michigan State Spartans rowing program, hasRosters, varsity athletes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRosters Context triple: [Michigan State Spartans rowing program, hasRosters, varsity athletes]
-
A.
hasRostersFor
chosen
Indicates that an entity maintains or provides one or more rosters associated with another entity, context, or time period.
-
B.
hasExpandedRoster
Indicates that an entity’s roster, lineup, or membership has increased in size compared to a previous state.
-
C.
activeRostersInclude
Indicates that a specified entity is currently listed as a member within another entity’s active roster.
-
D.
hasRosterStatus
Indicates the current membership or availability status of an entity within a defined roster or lineup.
-
E.
rosterBasis
Indicates the underlying criterion or rule used to determine which entities are included on a particular roster.
- 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fefa064ab48190925759950d0d94d9 |
completed | May 9, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69fef96ae5d08190b027435753c44821 |
completed | May 9, 2026, 9:07 a.m. |
Created at: May 3, 2026, 4:19 p.m.