Triple
T19840616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WNBA games |
E476715
|
entity |
| Predicate | rosterSizeLimit |
P3315
|
FINISHED |
| Object | 12 active players (typical) |
—
|
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: 12 active players (typical) | Statement: [WNBA games, rosterSizeLimit, 12 active players (typical)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rosterSizeLimit Context triple: [WNBA games, rosterSizeLimit, 12 active players (typical)]
-
A.
rosterSize
Indicates the total number of individuals included on a given roster.
-
B.
teamRosterLimit
chosen
Indicates the maximum number of members that are allowed to be on a team’s roster.
-
C.
hasMaximumNumberOfMembers
Indicates that there is an upper limit on how many members can be associated with a given entity.
-
D.
rosterSizeApprox
Indicates that the size of a group or roster is approximately equal to a specified number or range, allowing for minor variation.
-
E.
rosterLimitDivisionI
Indicates a restriction or cap on the number of participants allowed on a roster specifically for Division I.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6580576748190b85e234b01209ae7 |
completed | April 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.