Triple
T37989902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gusztáv Sebes |
E947795
|
entity |
| Predicate | notableEventManaged |
P153722
|
FINISHED |
| Object | England 3–6 Hungary match at Wembley in 1953 |
—
|
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: England 3–6 Hungary match at Wembley in 1953 | Statement: [Gusztáv Sebes, notableEventManaged, England 3–6 Hungary match at Wembley in 1953]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEventManaged Context triple: [Gusztáv Sebes, notableEventManaged, England 3–6 Hungary match at Wembley in 1953]
-
A.
notableEventServed
Indicates that an entity served in an official or significant capacity during a notable event.
-
B.
bearerNotableEvent
chosen
Indicates that a bearer (such as a person or entity) is associated with a specific notable event in which they played a significant role.
-
C.
notableManager
Indicates that an entity has, or is associated with, a manager who is particularly prominent, distinguished, or widely recognized.
-
D.
notableAIEvent
Indicates that an event is recognized as significant or influential within the field of artificial intelligence.
-
E.
notableEventIncluded
Indicates that a particular notable event is contained within, or forms part of, a larger collection, record, or 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.