Triple
T37856224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houston Roughnecks |
E944196
|
entity |
| Predicate | regularSeasonRecord2020 |
P196309
|
FINISHED |
| Object | 5–0 |
—
|
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: 5–0 | Statement: [Houston Roughnecks, regularSeasonRecord2020, 5–0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularSeasonRecord2020 Context triple: [Houston Roughnecks, regularSeasonRecord2020, 5–0]
-
A.
regularSeasonEndDate
Indicates the calendar date on which a regular season for a league, competition, or series of events concludes.
-
B.
seasonRecord
Indicates the overall performance or results an entity achieved over the course of a specific season (e.g., wins, losses, or comparable outcome metrics).
-
C.
regularSeasonRecord2016
Indicates the win-loss (and possibly tie) performance of an entity during the 2016 regular season.
-
D.
awayTeamRegularSeasonRecord
Indicates the win-loss (and possibly tie) record that the away team has accumulated during the regular season.
-
E.
regularSeasonConferenceRecord
Indicates the win-loss (and sometimes tie) record a team achieved in games played against opponents within its conference during the regular season.
- 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
| PDg | Predicate description generation | batch_69fe1fd58ad8819093d3d705e8521014 |
completed | May 8, 2026, 5:39 p.m. |
Created at: May 3, 2026, 4:19 p.m.