Triple
T23531333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rod Tidwell |
E576577
|
entity |
| Predicate | contractIssue |
P107087
|
FINISHED |
| Object | underpaid compared to other players |
—
|
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: underpaid compared to other players | Statement: [Rod Tidwell, contractIssue, underpaid compared to other players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contractIssue Context triple: [Rod Tidwell, contractIssue, underpaid compared to other players]
-
A.
contractFeature
Indicates that one entity is a feature, term, or provision that is included in or associated with a particular contract.
-
B.
contractValue
Indicates the monetary worth or agreed-upon financial amount specified in a contract between parties.
-
C.
contractUnit
Indicates that one entity serves as a contractual unit or party within a contract relationship involving another entity.
-
D.
disputeIssue
chosen
Indicates that there is a disagreement or conflict specifically concerning a particular issue or point of contention.
-
E.
causesContractWith
Indicates that one entity brings about or is responsible for the formation or existence of a contractual agreement with another entity.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ac78581c8190bd9d09ce2be8029d |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:09 p.m.