Triple
T3303792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL television packages |
E69397
|
entity |
| Predicate | haveTermLength |
P540
|
FINISHED |
| Object | multi-year contracts |
—
|
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: multi-year contracts | Statement: [NFL television packages, haveTermLength, multi-year contracts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveTermLength Context triple: [NFL television packages, haveTermLength, multi-year contracts]
-
A.
termLengthCondition
Indicates a condition or constraint specifying the required or allowed duration/length of a term (such as a contract, agreement, or period).
-
B.
termLength
chosen
Indicates the duration or period of time for which an agreement, position, or condition remains in effect.
-
C.
termLengthNumber
Indicates the numerical value representing the duration or length of a specified term.
-
D.
hasNoFixedTermLength
Indicates that the relationship or agreement exists without a predetermined or fixed duration for how long it will remain in effect.
-
E.
hasTerm
Indicates that an entity includes, is associated with, or is defined by a specific term or 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_69ad859f218081909458d2cebbf57565 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0c662308190aad8b2a93e1c8a5c |
completed | March 8, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.