Triple
T218251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glazer family |
E4155
|
entity |
| Predicate | acquisitionOfManchesterUnited |
P2617
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [Glazer family, acquisitionOfManchesterUnited, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquisitionOfManchesterUnited Context triple: [Glazer family, acquisitionOfManchesterUnited, 2005]
-
A.
acquiredSportsTeam
chosen
Indicates that one entity has purchased and taken ownership of a sports team from another party.
-
B.
acquisition
Indicates the act or relationship in which one entity obtains ownership or control of another entity, asset, or resource.
-
C.
acquiredByCity
Indicates that something (such as property, assets, or an organization) has been obtained or taken ownership of by a city.
-
D.
acquisitionType
Indicates the specific kind or category of acquisition relationship that exists between entities (such as a company buying another company, assets, or a controlling stake).
-
E.
mostSuccessfulClub
Indicates that one club holds the highest level of success (e.g., by titles, achievements, or performance) compared to all other clubs in the given context.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c5199d8819096736c11077adec3 |
completed | Feb. 28, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69a25b5357bc8190b29a48e3053fb76d |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.