Triple
T37923114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mighty Magyars |
E946016
|
entity |
| Predicate | unbeatenRunEnd |
P189806
|
FINISHED |
| Object | 1954 |
—
|
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: 1954 | Statement: [Mighty Magyars, unbeatenRunEnd, 1954]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unbeatenRunEnd Context triple: [Mighty Magyars, unbeatenRunEnd, 1954]
-
A.
unbeatenRunStart
Indicates the point in time or event at which an entity’s sequence of games or contests without defeat begins.
-
B.
unbeatenLeagueRunEndedAgainst
Indicates that a team's previously undefeated streak in league matches was ended in a match against a specific opponent.
-
C.
unbeatenLeagueRunEndMatchVenue
Indicates the venue where a team's previously unbeaten league run came to an end in a specific match.
-
D.
unbeatenStreakLength
Indicates the length of a continuous sequence during which an entity has not been defeated or has remained without a loss.
-
E.
runnerUpUndefeatedEnteringFinal
Indicates that an entity finished as runner-up in a competition despite having been undefeated up to the final match or round.
- 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc993caa881908c16c3e21efaeef9 |
completed | May 6, 2026, 11:07 p.m. |
Created at: May 3, 2026, 4:20 p.m.