Triple
T2210312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFC East rivalry |
E50900
|
entity |
| Predicate | oftenInfluences |
P9
|
FINISHED |
| Object | NFC playoff seeding |
—
|
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: NFC playoff seeding | Statement: [NFC East rivalry, oftenInfluences, NFC playoff seeding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenInfluences Context triple: [NFC East rivalry, oftenInfluences, NFC playoff seeding]
-
A.
typeOfInfluence
Indicates the specific nature or category of influence that one entity exerts on another.
-
B.
influenced
chosen
Indicates that one entity has affected, shaped, or altered another entity’s state, behavior, or characteristics.
-
C.
placeOfInfluence
Indicates the location or area where an entity exerts significant impact, authority, or cultural, social, or intellectual influence.
-
D.
hasPopularityInfluencedBy
Indicates that the popularity level of one entity is affected or shaped by another specified factor or entity.
-
E.
influencedDiscussionOf
Indicates that one entity had an effect on the way another entity was discussed, framed, or debated.
- 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_69a88b06709c8190978fb2418470d1b6 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfce5abc8190b90b92e32045385d |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbdaa26d48190860c33fd464c4845 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.