Triple
T3047317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ManningCast |
E83479
|
entity |
| Predicate | airingPattern |
P45318
|
FINISHED |
| Object | select Monday Night Football games |
—
|
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: select Monday Night Football games | Statement: [ManningCast, airingPattern, select Monday Night Football games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airingPattern Context triple: [ManningCast, airingPattern, select Monday Night Football games]
-
A.
kitPattern
Indicates the design or visual pattern featured on a team's kit or uniform.
-
B.
pattern
Indicates that one entity exhibits, follows, or is characterized by a particular recurring form, structure, or arrangement associated with another entity.
-
C.
camouflagePattern
Indicates that one entity has a surface or visual design intended to conceal it by blending with its surroundings or disrupting its outline.
-
D.
hatPattern
Indicates that one entity has a hat characterized by a specific pattern or design.
-
E.
roofPatternInspiredBy
Indicates that the design or arrangement of a roof follows or is derived from a particular pattern, style, or source of inspiration.
- 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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9bad11b48190a5bd01e91a320e14 |
completed | March 8, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69ad962195388190856013a2519c2b0f |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad9b272a408190ba0ce09bdeea76c9 |
completed | March 8, 2026, 3:52 p.m. |
Created at: March 8, 2026, 3:01 p.m.