Triple
T28014813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jordan Love |
E707517
|
entity |
| Predicate | jerseyNumberPreviouslyWornInCollege |
P2651
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Jordan Love, jerseyNumberPreviouslyWornInCollege, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jerseyNumberPreviouslyWornInCollege Context triple: [Jordan Love, jerseyNumberPreviouslyWornInCollege, 10]
-
A.
retiredJerseyCollege
Indicates that a college has formally retired a particular jersey number, typically in honor of a former player or coach associated with that institution.
-
B.
jerseyNumber
chosen
Indicates the specific uniform number assigned to and worn by an individual, typically in a sports context.
-
C.
playedForCollegeTeamUntil
Indicates that an individual was a member of and played for a specific college team up to (and including) a particular end date or season.
-
D.
playedForCollegeTeamFrom
Indicates that an individual was a member of and played for a specific college team starting in a given year.
-
E.
positionPlayedInCollege
Indicates the specific playing position an individual held on a sports team during their college career.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 8:06 p.m.