Triple
T25591858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Back from the Brink |
E641543
|
entity |
| Predicate | describesClub |
P163841
|
FINISHED |
| Object | Manchester United F.C. |
—
|
NE NERFINISHED |
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: Manchester United F.C. | Statement: [Back from the Brink, describesClub, Manchester United F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesClub Context triple: [Back from the Brink, describesClub, Manchester United F.C.]
-
A.
involvesClub
Indicates that an action, event, or relationship includes or is associated with a specific club as a participating entity.
-
B.
representsClub
Indicates that one entity serves as an official representative or delegate of a particular club.
-
C.
privateClub
Indicates that an entity is a club or organization whose membership or access is restricted to selected or approved individuals rather than being open to the general public.
-
D.
clubRebrandedAs
Indicates that a sports club has changed its official name or identity to become another specified club.
-
E.
mainClub2
Indicates that an entity serves as the primary or main club associated with another entity (such as a person, player, or organization).
- F. None of above. chosen
Provenance (4 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 21, 2026, 4:25 p.m.