Triple
T9146918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wes Morgan |
E219478
|
entity |
| Predicate | jerseyNumberAtLeicesterCity |
P2651
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Wes Morgan, jerseyNumberAtLeicesterCity, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jerseyNumberAtLeicesterCity Context triple: [Wes Morgan, jerseyNumberAtLeicesterCity, 5]
-
A.
jerseyNumber
chosen
Indicates the specific uniform number assigned to and worn by an individual, typically in a sports context.
-
B.
jerseyNumberManaged
Indicates that an entity is responsible for assigning, organizing, or overseeing jersey numbers for players or team members.
-
C.
hasJerseyNumberRetired
Indicates that an entity has had its jersey number officially retired, typically in recognition of its contributions or achievements.
-
D.
jerseyNumberStyle
Indicates the visual design or formatting style used for displaying a player’s jersey number.
-
E.
wearsJerseyFor
Indicates that one entity wears a jersey representing, belonging to, or in support of another entity (such as a team, organization, or individual).
- 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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca918a3c881909c34a6a682eb2625 |
completed | April 1, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:20 p.m.