Triple
T541335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFC South |
E12635
|
entity |
| Predicate | realignment |
P3196
|
FINISHED |
| Object | Created during 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: Created during 2002 NFL realignment | Statement: [AFC South, realignment, Created during 2002 NFL realignment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realignment Context triple: [AFC South, realignment, Created during 2002 NFL realignment]
-
A.
relocated
Indicates that an entity has moved or been moved from one location or position to another.
-
B.
alignmentChange
Indicates a change in the moral, ethical, or factional stance of an entity relative to its previous alignment.
-
C.
divisionRealignment
chosen
Indicates a reorganization of how entities are grouped into divisions, typically involving changes to which entities belong to which division.
-
D.
reorganizedIn
Indicates that an entity underwent a structural or organizational change within a specified context, time, or framework.
-
E.
reform
Indicates bringing about significant changes to an existing system, practice, or entity in order to improve or correct it.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49861195081909540eaf402a5401a |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b67c308190a1a225ab7c4b74c6 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.