Triple
T405296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryce Harper |
E9369
|
entity |
| Predicate | formerJerseyNumber |
P2651
|
FINISHED |
| Object | 34 |
—
|
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: 34 | Statement: [Bryce Harper, formerJerseyNumber, 34]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerJerseyNumber Context triple: [Bryce Harper, formerJerseyNumber, 34]
-
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.
retiredNumber
Indicates that an entity (typically a team or organization) has formally withdrawn a specific number from future use, usually to honor a particular individual or achievement associated with that number.
-
D.
retiredNumberHonoree
Indicates that an entity is honored by having its jersey or identification number formally retired by a team or organization.
-
E.
hasInsigniaWornBy
Indicates that a particular insignia is worn by a specified entity (such as a person, group, or organization).
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eca37fe881909802126952dfdd59 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e97066e8819083cc1b3a421b9650 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.