Triple
T5287514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL Collective Bargaining Agreement |
E119655
|
entity |
| Predicate | isPeriodicallyRenegotiated |
P55684
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NFL Collective Bargaining Agreement, isPeriodicallyRenegotiated, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPeriodicallyRenegotiated Context triple: [NFL Collective Bargaining Agreement, isPeriodicallyRenegotiated, true]
-
A.
periodicallyRenegotiated
chosen
Indicates that the terms or conditions of a relationship, agreement, or arrangement are reviewed and adjusted at regular, recurring intervals.
-
B.
isRenewable
Indicates that a resource or energy source can be naturally replenished or regenerated within a human-relevant timescale.
-
C.
laterRenewedFor
Indicates that an existing agreement, contract, or arrangement was renewed again at a subsequent, later time.
-
D.
tienePeriodicidad
Indicates that something occurs, recurs, or is scheduled with a specific regular frequency or periodic pattern.
-
E.
renewalRequired
Indicates that an existing agreement, status, or authorization must be renewed to remain valid.
- 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_69bd446de5648190b313a90bd96730d2 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8682d18c8190bbb35cc75c8a7c12 |
completed | March 20, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69bd844dfdac819086efedd1cbebff84 |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:52 p.m.