Triple
T1875314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston Red Sox spring training games |
E39129
|
entity |
| Predicate | rosterRule |
P8188
|
FINISHED |
| Object | allow expanded rosters |
—
|
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: allow expanded rosters | Statement: [Boston Red Sox spring training games, rosterRule, allow expanded rosters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rosterRule Context triple: [Boston Red Sox spring training games, rosterRule, allow expanded rosters]
-
A.
rosterRequirement
Indicates that one entity specifies or imposes a required composition, number, or type of participants that must be included in another entity’s roster.
-
B.
setsRulesFor
chosen
Indicates that one entity establishes or defines rules, guidelines, or constraints that another entity is expected to follow.
-
C.
rosterSize
Indicates the total number of individuals included on a given roster.
-
D.
eligibilityRulesSetBy
Indicates that one party defines or establishes the criteria or rules determining another party’s eligibility for something.
-
E.
involvesRuler
Indicates that the relationship or action includes or pertains to a ruler as a participating party.
- 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_69a8862f7074819096afe7fe65e179e9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb0f79fbc819085c54f3189a552d9 |
completed | March 7, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69abafe2b56c81909e13d543982e6e13 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.