Triple
T14320532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA Women’s Rowing Championship |
E355072
|
entity |
| Predicate | teamSizeContext |
P3668
|
FINISHED |
| Object | varsity women’s rowing programs |
—
|
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 women’s rowing programs | Statement: [NCAA Women’s Rowing Championship, teamSizeContext, varsity women’s rowing programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamSizeContext Context triple: [NCAA Women’s Rowing Championship, teamSizeContext, varsity women’s rowing programs]
-
A.
typicalTeamSize
chosen
Indicates the usual or most common number of members that make up a given team.
-
B.
collaborationSize
Indicates the number of participants involved together in a given collaborative relationship or activity.
-
C.
teamNumberContext
Indicates that a specific team number is associated with or interpreted within a particular contextual setting or scope.
-
D.
staffSize
Indicates the number of staff members associated with an entity.
-
E.
teamConstraint
Indicates a rule or limitation governing how entities can be grouped, associated, or operate together as a team.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de883bf71c8190a9a092a025cf98f0 |
completed | April 14, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:13 a.m.