Triple
T3807822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlanta Falcons–New Orleans Saints rivalry |
E93051
|
entity |
| Predicate | hasFanBaseNicknameForFalcons |
P49044
|
FINISHED |
| Object | Falcons fans |
—
|
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: Falcons fans | Statement: [Atlanta Falcons–New Orleans Saints rivalry, hasFanBaseNicknameForFalcons, Falcons fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFanBaseNicknameForFalcons Context triple: [Atlanta Falcons–New Orleans Saints rivalry, hasFanBaseNicknameForFalcons, Falcons fans]
-
A.
cityNickNameForFanBase
Indicates that a particular nickname is used by fans to refer to a city or its fan base.
-
B.
notableTeamNickname
Indicates that a team is commonly known by a particular nickname that is notable or widely recognized.
-
C.
teamNickname
Indicates the commonly used informal or symbolic name by which a team is known.
-
D.
nicknamedFor
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
-
E.
supporterGroupNickname
chosen
Indicates that a particular nickname is used to refer to a group of supporters associated with an entity.
- 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.