Triple
T27006189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Jets |
E680246
|
entity |
| Predicate | superBowlIIIResult |
P2482
|
FINISHED |
| Object | defeated Baltimore Colts |
—
|
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: defeated Baltimore Colts | Statement: [New York Jets, superBowlIIIResult, defeated Baltimore Colts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: superBowlIIIResult Context triple: [New York Jets, superBowlIIIResult, defeated Baltimore Colts]
-
A.
superBowlIIISeason
Indicates the specific sports season in which Super Bowl III was played or concluded.
-
B.
superBowlIIIOpponent
chosen
Indicates the opposing team that a given team faced in Super Bowl III.
-
C.
SuperBowlXXXResult
Indicates the outcome or final result of the game played in Super Bowl XXX between the participating teams.
-
D.
superBowlXXXVResult
Indicates the outcome of Super Bowl XXXV, specifying which team won or lost and possibly the final score.
-
E.
SuperBowlXVIIIResult
Indicates the outcome of Super Bowl XVIII, relating the competing teams to the final score and winner of that specific game.
- 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_69eeeb53939c8190bd431f32b060f01f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 7:01 a.m.