Triple
T1357703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1994–95 MLB strike |
E29025
|
entity |
| Predicate | counterparty |
P378
|
FINISHED |
| Object | Major League Baseball team owners |
—
|
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: Major League Baseball team owners | Statement: [1994–95 MLB strike, counterparty, Major League Baseball team owners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: counterparty Context triple: [1994–95 MLB strike, counterparty, Major League Baseball team owners]
-
A.
negotiatingParty
chosen
Indicates that an entity is actively involved as a participant in a negotiation process with another entity.
-
B.
hasCounterpart
Indicates that one entity corresponds to, matches, or serves as an equivalent or parallel version of another entity.
-
C.
nonSignatoryParty
Indicates that an entity is a party related to an agreement or treaty without having formally signed or acceded to it.
-
D.
participatingParty
Indicates that an entity is involved as a participant in a particular event, activity, or transaction.
-
E.
loserParty
Indicates that a particular political party was the one that lost in a given election or contest.
- 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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c28db5048190a279ee9882caaeaf |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef7700c819099b294e8d9320e70 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.