Triple
T9212419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlie Scott |
E221154
|
entity |
| Predicate | representedBySportsNumber |
P2651
|
FINISHED |
| Object | 11 with Boston Celtics |
—
|
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: 11 with Boston Celtics | Statement: [Charlie Scott, representedBySportsNumber, 11 with Boston Celtics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representedBySportsNumber Context triple: [Charlie Scott, representedBySportsNumber, 11 with Boston Celtics]
-
A.
jerseyNumber
chosen
Indicates the specific uniform number assigned to and worn by an individual, typically in a sports context.
-
B.
representedByTeam
Indicates that an entity is officially or formally represented by a specific team.
-
C.
leagueRetiredNumberBy
Indicates that a sports league has officially retired a specific jersey number in honor of a particular person or entity.
-
D.
hasJerseyNumberRetired
Indicates that an entity has had its jersey number officially retired, typically in recognition of its contributions or achievements.
-
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_69ca83e9d0e081908bdb71097201a06c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda05406081909893bec3a092d3ce |
completed | April 1, 2026, 8:40 a.m. |
| PD | Predicate disambiguation | batch_69cc660ce23c81909c7bbe10f4a05f36 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:27 p.m.