Triple
T27634852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikal Bridges |
E696440
|
entity |
| Predicate | offensiveSkill |
P163309
|
FINISHED |
| Object | spot-up shooting |
—
|
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: spot-up shooting | Statement: [Mikal Bridges, offensiveSkill, spot-up shooting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offensiveSkill Context triple: [Mikal Bridges, offensiveSkill, spot-up shooting]
-
A.
offensiveStrategy
Indicates a strategic approach focused on attacking or aggressively advancing against an opponent.
-
B.
offensiveStrength
Indicates the degree or capacity of an entity to carry out effective attacks or aggressive actions against an opponent.
-
C.
offensiveCharacteristic
Indicates that one entity possesses a trait, behavior, or quality that is considered insulting, disrespectful, or likely to cause offense to another entity or group.
-
D.
attackEffect
Indicates that one entity’s attack produces a specific effect or consequence on another entity.
-
E.
offensiveForce
Indicates the use or application of aggressive or attacking power or violence by one entity against another.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6369a22688190a5674191c90a5d12 |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6359d46b88190922dd7de508e3b0e |
completed | May 2, 2026, 5:34 p.m. |
Created at: April 27, 2026, 2:23 p.m.