Triple
T2195202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL Competition Committee |
E49956
|
entity |
| Predicate | proposesChangesTo |
P21476
|
FINISHED |
| Object | NFL Bylaws |
—
|
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 Bylaws | Statement: [NFL Competition Committee, proposesChangesTo, NFL Bylaws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposesChangesTo Context triple: [NFL Competition Committee, proposesChangesTo, NFL Bylaws]
-
A.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
-
B.
proposedAmendment
chosen
Indicates that one entity has formally suggested a change or addition (an amendment) to another entity, such as a document, law, or agreement.
-
C.
changeRequestsImplementedBy
Indicates that the specified change requests have been carried out or fulfilled by the referenced implementing entity.
-
D.
claimsToModify
Indicates that one entity asserts it can change, alter, or adjust another entity or its properties.
-
E.
notableChange
Indicates a significant alteration or shift in the state, condition, or characteristics of an entity or relationship.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf764e348190896af2aeb5520038 |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbda52328819089c7ab111bebb0ca |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.