Triple
T12278931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1933 NFL Championship Game |
E292662
|
entity |
| Predicate | regulationLength |
P25687
|
FINISHED |
| Object | 60 minutes |
—
|
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: 60 minutes | Statement: [1933 NFL Championship Game, regulationLength, 60 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulationLength Context triple: [1933 NFL Championship Game, regulationLength, 60 minutes]
-
A.
lengthRegime
Indicates a specific range or category of length within which something operates, is measured, or is classified.
-
B.
hasRegulationSize
Indicates that something conforms to an officially defined or standard size specified by rules or regulations.
-
C.
properLengthMeasuredIn
Indicates that the proper (intrinsic or rest-frame) length of an entity is expressed using a specified unit of measurement.
-
D.
regulationMinutes
chosen
Indicates the number of minutes played during the standard regulation period of a game, excluding any overtime or extra periods.
-
E.
regulationCharacteristic
Indicates that one entity specifies, defines, or constrains a particular characteristic or property of another through a rule, standard, or regulatory condition.
- 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9261e1570819084bb4fdb44aa6aea |
completed | April 10, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69d91c4d9a9c8190aeb7beaf9792d8f0 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.