Triple
T36134358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1971 Nebraska vs. Oklahoma football game |
E1045119
|
entity |
| Predicate | NebraskaOffenseType |
P185378
|
FINISHED |
| Object | balanced offense |
—
|
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: balanced offense | Statement: [1971 Nebraska vs. Oklahoma football game, NebraskaOffenseType, balanced offense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NebraskaOffenseType Context triple: [1971 Nebraska vs. Oklahoma football game, NebraskaOffenseType, balanced offense]
-
A.
offensivePlayType
Indicates the specific type of offensive play that is being executed or has occurred within a game or sporting context.
-
B.
playsRoleInOffense
Indicates that an entity performs a specific function or position within an offensive strategy or system.
-
C.
offensiveTackle
Indicates that an entity plays the offensive tackle position, responsible for blocking and protecting on the offensive line in a gridiron football context.
-
D.
offensiveCoordinator
Indicates that one entity serves as the offensive coordinator (the coach responsible for directing the offensive unit) for another entity, typically a sports team.
-
E.
offensiveSchemeRunnerUp
Indicates that an offensive scheme finished in second place or was the runner-up in a particular ranking, contest, or evaluation.
- 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_69f76e36a4508190b5bfc8f594272a4c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be520f148190ba200bf3dbf40656 |
completed | May 3, 2026, 9:29 p.m. |
Created at: May 3, 2026, 4:08 p.m.