Triple
T194834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Football League |
E3795
|
entity |
| Predicate | postMergerConsequence |
P812
|
FINISHED |
| Object | NFL conference 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: NFL conference realignment | Statement: [American Football League, postMergerConsequence, NFL conference realignment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postMergerConsequence Context triple: [American Football League, postMergerConsequence, NFL conference realignment]
-
A.
reasonForMerger
Indicates the underlying cause, motivation, or justification for why two or more entities merged.
-
B.
mergedInto
Indicates that one entity has been combined with and absorbed into another entity, ceasing to exist as a separate unit.
-
C.
confluenceWith
Indicates that one entity joins or merges together with another, typically at a shared meeting point.
-
D.
hasConsequence
chosen
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
-
E.
rejectedOrModifiedBy
Indicates that a proposal, request, or item was either not accepted as-is or was altered by a particular agent or authority.
- 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a25969425081908e178db8ba4631c2 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a25677da14819094cd02868fd30c83 |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.