Triple
T2523289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLS Newcomer of the Year Award |
E55573
|
entity |
| Predicate | teamRestriction |
P18786
|
FINISHED |
| Object | open to players from all MLS clubs |
—
|
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: open to players from all MLS clubs | Statement: [MLS Newcomer of the Year Award, teamRestriction, open to players from all MLS clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamRestriction Context triple: [MLS Newcomer of the Year Award, teamRestriction, open to players from all MLS clubs]
-
A.
squadRestrictionForInvitedTeams
Indicates a constraint or rule that applies to the squad composition or size specifically for teams that have been invited.
-
B.
teamEligibility
chosen
Indicates whether an entity meets the required conditions to participate as a member of a particular team.
-
C.
includesTeam
Indicates that a group, project, or organization has a specific team as one of its constituent members or components.
-
D.
teamLimitPerAssociation
Indicates the maximum number of teams that can be associated with a single association or grouping.
-
E.
memberTeam
Indicates that an entity belongs to or is part of a specific team.
- 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_69ab49e4749c8190813311efd1630f1b |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd23a0a548190b44393e0f823f7a9 |
completed | March 7, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69abd0c144b0819092f32a13c1d127e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.