Triple
T34075559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mason Greenwood |
E873897
|
entity |
| Predicate | seniorDebutForManchesterUnited |
P101684
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Mason Greenwood, seniorDebutForManchesterUnited, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seniorDebutForManchesterUnited Context triple: [Mason Greenwood, seniorDebutForManchesterUnited, 2019]
-
A.
leagueDebutForManchesterUnited
Indicates that an entity made their first league appearance while playing for Manchester United.
-
B.
joinedManchesterUnited
Indicates that an entity became a member of, or signed to play for, Manchester United.
-
C.
notablePlayerManchesterUnited
Indicates that the subject is a player who is notably associated with Manchester United, typically through significant contribution or recognition while at the club.
-
D.
manchesterUnitedCaptain
Indicates that the subject is the designated team captain of Manchester United Football Club at a given time.
-
E.
debutedForClub
chosen
Indicates that an entity made its first official appearance or start as a player for a particular sports club.
- 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70bd1c5908190882085d458dba048 |
completed | May 3, 2026, 8:48 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:52 a.m.