Triple
T3807811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlanta Falcons–New Orleans Saints rivalry |
E93051
|
entity |
| Predicate | firstMeetingContext |
P44676
|
FINISHED |
| Object | regular season game |
—
|
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: regular season game | Statement: [Atlanta Falcons–New Orleans Saints rivalry, firstMeetingContext, regular season game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMeetingContext Context triple: [Atlanta Falcons–New Orleans Saints rivalry, firstMeetingContext, regular season game]
-
A.
firstMeetingSeason
Indicates the season of the year during which two entities first met.
-
B.
firstMeetingScore
Indicates the evaluated quality or outcome of an entity’s initial meeting or first interaction with another entity.
-
C.
meetingContext
chosen
Indicates the situational setting, circumstances, or background conditions in which a meeting takes place.
-
D.
firstMeetingYear
Indicates the calendar year in which two entities first met or had their initial encounter.
-
E.
firstSessionStart
Indicates the point in time when an entity’s very first session or interaction begins.
- 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_69aed96a60088190ab1df8390fffc935 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aee8db8a288190afd1e3b9dcf02e97 |
completed | March 9, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69aee7461abc8190945716f4b93e1a18 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:16 p.m.