Triple
T32404245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2003 MLS SuperDraft |
E828032
|
entity |
| Predicate | usedByTeams |
P189356
|
FINISHED |
| Object | to build rosters for the 2003 MLS season |
—
|
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: to build rosters for the 2003 MLS season | Statement: [2003 MLS SuperDraft, usedByTeams, to build rosters for the 2003 MLS season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByTeams Context triple: [2003 MLS SuperDraft, usedByTeams, to build rosters for the 2003 MLS season]
-
A.
usedByTeam
Indicates that something (such as a resource, tool, or method) is utilized or employed by a particular team.
-
B.
usedForTeam
Indicates that something is utilized or designated for use by a particular team.
-
C.
usedForTeamInState
Indicates that something serves as a team or is utilized by a team within a specified state or jurisdiction.
-
D.
associatedTeam
Indicates that one entity is linked or connected to a particular team, typically as its member, owner, or primary affiliation.
-
E.
usedDuringTeam
Indicates that something is utilized or applied in the context of a team activity, process, or collaboration.
- F. None of above. chosen
Provenance (4 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbc48b75c8190bec27dd4b7de797f |
completed | May 6, 2026, 10:10 p.m. |
Created at: May 1, 2026, 12:53 a.m.