Triple
T1331901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1981 MLB strike |
E28660
|
entity |
| Predicate | typeOfDispute |
P26178
|
FINISHED |
| Object | free agent compensation system |
—
|
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: free agent compensation system | Statement: [1981 MLB strike, typeOfDispute, free agent compensation system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDispute Context triple: [1981 MLB strike, typeOfDispute, free agent compensation system]
-
A.
disputeInvolves
chosen
Indicates that a particular dispute includes or concerns the specified entities as participants or parties to the conflict.
-
B.
typeOfClaim
Indicates the specific category or nature of a claim being made in relation to an entity or statement.
-
C.
typeOfLaw
Indicates that one entity is a specific category or kind of law to which the other entity pertains.
-
D.
legalCase
Indicates a relationship where a formal legal dispute or proceeding exists between parties, typically adjudicated by a court or similar authority.
-
E.
methodOfDisputeResolution
Indicates the process or mechanism used to settle a disagreement or conflict between parties.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1c5f86c819098e98b046968954a |
completed | March 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69a4beef6a188190996f8775bdda8f6c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.