Triple
T3164688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bo Jackson |
E66182
|
entity |
| Predicate | jerseyNumberMLB |
P2651
|
FINISHED |
| Object | 16 |
—
|
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: 16 | Statement: [Bo Jackson, jerseyNumberMLB, 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jerseyNumberMLB Context triple: [Bo Jackson, jerseyNumberMLB, 16]
-
A.
jerseyNumber
chosen
Indicates the specific uniform number assigned to and worn by an individual, typically in a sports context.
-
B.
leagueRetiredNumberBy
Indicates that a sports league has officially retired a specific jersey number in honor of a particular person or entity.
-
C.
wearsJerseyFor
Indicates that one entity wears a jersey representing, belonging to, or in support of another entity (such as a team, organization, or individual).
-
D.
allowsMLBPlayers
Indicates that one entity grants permission or authorization for Major League Baseball players to participate in, access, or make use of another entity or activity.
-
E.
teamNumberWithBostonRedSox
Indicates that an entity has a team number specifically associated with the Boston Red Sox.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada61ba98881909106951c8ceeb959 |
completed | March 8, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfe0a948190928f2201d671c654 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.