Triple
T1327867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1972 MLB strike |
E28370
|
entity |
| Predicate | collectiveBargainingAgreement |
P611
|
FINISHED |
| Object | 1972 MLB basic agreement |
—
|
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: 1972 MLB basic agreement | Statement: [1972 MLB strike, collectiveBargainingAgreement, 1972 MLB basic agreement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectiveBargainingAgreement Context triple: [1972 MLB strike, collectiveBargainingAgreement, 1972 MLB basic agreement]
-
A.
laborUnion
Indicates that an entity is a labor union representing workers in collective employment-related matters.
-
B.
agreement
chosen
Indicates that two or more parties mutually consent to and accept shared terms, conditions, or understandings.
-
C.
basedOnAgreementWith
Indicates that something exists, is done, or is determined on the basis of a prior agreement or accord between the involved parties.
-
D.
negotiationAssociatedWith
Indicates a relationship where a negotiation is connected to, involves, or is conducted by a particular entity (such as a person, organization, or group).
-
E.
agreementSigned
Indicates that a formal agreement or contract has been officially signed and accepted by the involved 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1c1d8188190b15a641a08345adc |
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.