Triple
T24744399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1981 NFL season |
E618653
|
entity |
| Predicate | TheCatchTeams |
P131747
|
FINISHED |
| Object | San Francisco 49ers vs. Dallas Cowboys |
—
|
NE NERFINISHED |
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: San Francisco 49ers vs. Dallas Cowboys | Statement: [1981 NFL season, TheCatchTeams, San Francisco 49ers vs. Dallas Cowboys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TheCatchTeams Context triple: [1981 NFL season, TheCatchTeams, San Francisco 49ers vs. Dallas Cowboys]
-
A.
featuredTeam
Indicates that a particular team is highlighted or given special prominence in a given context or presentation.
-
B.
coreTeams
Indicates that the entities are part of the same primary or central team within an organization or project.
-
C.
stateTeam
Indicates that a team is officially associated with, represents, or belongs to a particular state.
-
D.
featuresTeams
chosen
Indicates that something prominently presents or includes specific teams as a central element or focus.
-
E.
AllStarTeam
Indicates that an entity has been selected for inclusion on an all-star team, recognizing it as one of the top performers within a league, season, or competition.
- 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_69e2fab8f95c81908bb9e552cf3280c2 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a25ab88190a72db43043c1f6ff |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:20 a.m.