Triple
T4385474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arizona Cardinals–Seattle Seahawks rivalry |
E99230
|
entity |
| Predicate | reasonForIncreasedFrequency |
P56290
|
FINISHED |
| Object | 2002 NFL realignment |
—
|
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: 2002 NFL realignment | Statement: [Arizona Cardinals–Seattle Seahawks rivalry, reasonForIncreasedFrequency, 2002 NFL realignment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForIncreasedFrequency Context triple: [Arizona Cardinals–Seattle Seahawks rivalry, reasonForIncreasedFrequency, 2002 NFL realignment]
-
A.
laterFrequency
Indicates that one event, state, or action occurs with a lower frequency than another in a temporal sequence.
-
B.
usesFrequency
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
-
C.
isFrequently
Indicates that an action, state, or relationship occurs often or with high regularity between the related entities.
-
D.
serviceFrequencyType
Indicates how often a service occurs or is scheduled within a given time period.
-
E.
frequentOccasion
Indicates that a particular event, situation, or condition occurs repeatedly or commonly over time.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35264e44c81908dd0e0a81f1353bb |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3501834448190bedf775a80da4778 |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:19 p.m.