Triple
T7891042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikal Bridges |
E183232
|
entity |
| Predicate | jerseyNumberWithBrooklynNets |
P2651
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Mikal Bridges, jerseyNumberWithBrooklynNets, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jerseyNumberWithBrooklynNets Context triple: [Mikal Bridges, jerseyNumberWithBrooklynNets, 1]
-
A.
jerseyNumber
chosen
Indicates the specific uniform number assigned to and worn by an individual, typically in a sports context.
-
B.
jerseyNumberRetiredInHisHonor
Indicates that a person’s jersey number has been officially retired by a team or organization as a tribute to that person’s contributions or legacy.
-
C.
retiredJerseyNumberByTeam
Indicates that a sports team has officially retired a specific jersey number in honor of a player or figure, making it unavailable for future use by team members.
-
D.
jerseyNumberManaged
Indicates that an entity is responsible for assigning, organizing, or overseeing jersey numbers for players or team members.
-
E.
jerseyNumberStyle
Indicates the visual design or formatting style used for displaying a player’s jersey number.
- 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39ee137081908e87e35016c3a176 |
completed | March 31, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69cae92b0cd881908e715a10d3252e83 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5 p.m.