Triple
T8318462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern League |
E194765
|
entity |
| Predicate | teamLimitPerMLBClub |
P30934
|
FINISHED |
| Object | one Double-A affiliate |
—
|
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: one Double-A affiliate | Statement: [Eastern League, teamLimitPerMLBClub, one Double-A affiliate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamLimitPerMLBClub Context triple: [Eastern League, teamLimitPerMLBClub, one Double-A affiliate]
-
A.
teamRosterLimit
Indicates the maximum number of members that are allowed to be on a team’s roster.
-
B.
teamLimitPerAssociation
chosen
Indicates the maximum number of teams that can be associated with a single association or grouping.
-
C.
teamLimitPerInstitution
Indicates a restriction on the maximum number of teams that may come from a single institution.
-
D.
teamConstraint
Indicates a rule or limitation governing how entities can be grouped, associated, or operate together as a team.
-
E.
minorLeagueManagerFor
Indicates that one entity serves as the manager of a minor league team associated with another entity (typically a professional sports organization).
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f648e10819081ad1fed870b2b86 |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bf689c8190a9d9b6b872abf53d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:55 p.m.