Triple
T31004105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Cup match vs Red Star Belgrade |
E790017
|
entity |
| Predicate | aggregateContext |
P170897
|
FINISHED |
| Object |
Manchester United were defending a first-leg lead
Manchester United were defending a first-leg lead refers to the situation in a European Cup tie against Red Star Belgrade where Manchester United entered the second leg with an advantage from the first match and focused on preserving or building on that lead to progress.
|
E1942767
|
NE FINISHED |
How this triple was built (3 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 were defending a first-leg lead | Statement: [European Cup match vs Red Star Belgrade, aggregateContext, Manchester United were defending a first-leg lead]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Manchester United were defending a first-leg lead Triple: [European Cup match vs Red Star Belgrade, aggregateContext, Manchester United were defending a first-leg lead]
Generated description
Manchester United were defending a first-leg lead refers to the situation in a European Cup tie against Red Star Belgrade where Manchester United entered the second leg with an advantage from the first match and focused on preserving or building on that lead to progress.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aggregateContext Context triple: [European Cup match vs Red Star Belgrade, aggregateContext, Manchester United were defending a first-leg lead]
-
A.
collectionContext
Indicates the situational or environmental framework within which a collection is formed, used, or interpreted, specifying the circumstances that give meaning to the act of collecting or the collected items.
-
B.
bindingContext
Indicates the contextual or situational conditions under which one entity is bound or associated to another (e.g., scope, environment, or circumstances of the binding).
-
C.
organizedInContextOf
Indicates that an event or activity was arranged or carried out specifically within, and in relation to, a particular situational, thematic, or institutional context.
-
D.
contextOfComposition
Indicates the situational, cultural, or environmental circumstances in which a composition or work was created.
-
E.
integrationContext
Indicates the contextual framework or environment within which multiple components, systems, or processes are combined and interact as an integrated whole.
- F. None of above. chosen
Provenance (7 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a29183441a881909b5d2da676433345 |
completed | June 10, 2026, 7:54 a.m. |
| NEDg | Description generation | batch_6a2918f4ee448190baf0697c0a4bac1c |
completed | June 10, 2026, 7:57 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a291bbf5db88190b416bbf549343a86 |
completed | June 10, 2026, 8:09 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:57 p.m.