Triple
T4822611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vince Lombardi |
E107743
|
entity |
| Predicate | GreenBayPackersRegularSeasonRecord |
P44267
|
FINISHED |
| Object | 89–29–4 |
—
|
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: 89–29–4 | Statement: [Vince Lombardi, GreenBayPackersRegularSeasonRecord, 89–29–4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GreenBayPackersRegularSeasonRecord Context triple: [Vince Lombardi, GreenBayPackersRegularSeasonRecord, 89–29–4]
-
A.
EaglesRegularSeasonRecord
Indicates the win-loss (and possibly tie) performance of the Eagles during a specific regular season.
-
B.
nflRecord
chosen
Indicates the win-loss-tie performance record a team or individual has accumulated in NFL competition.
-
C.
GiantsRegularSeasonRecordEnteringGame
Indicates the Giants’ cumulative regular-season win–loss record at the time a particular game begins.
-
D.
ChicagoPackersSeason
Indicates the relationship between the Chicago Packers team and a specific basketball season in which they competed.
-
E.
RedskinsRecordRegularSeason
Indicates the win-loss-tie record achieved by the Washington Redskins during a specific NFL regular season.
- 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_69bd43f9efa081908314cb3e94fa1695 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1fe130819087ae01309f96a0c8 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.