Triple
T425523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rutgers Scarlet Knights women’s basketball |
E8198
|
entity |
| Predicate | playingStyle |
P3775
|
FINISHED |
| Object | strong defensive play |
—
|
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: strong defensive play | Statement: [Rutgers Scarlet Knights women’s basketball, playingStyle, strong defensive play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playingStyle Context triple: [Rutgers Scarlet Knights women’s basketball, playingStyle, strong defensive play]
-
A.
styleOfPlay
chosen
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
-
B.
choreographyStyle
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
-
C.
hasRhythmicStyle
Indicates that one entity exhibits or is characterized by a particular rhythmic pattern or style in its expression or behavior.
-
D.
flightStyle
Indicates the characteristic manner or pattern in which an entity performs or exhibits flight.
-
E.
playingPosition
Indicates the specific role or position an individual occupies while participating in a game or sport.
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eed56ab481909eec289075496260 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd6736c81909a6ca549f77b4345 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.