Triple
T32404226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2003 MLS SuperDraft |
E828032
|
entity |
| Predicate | selectionPoolIncludes |
P162905
|
FINISHED |
| Object | college players |
—
|
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: college players | Statement: [2003 MLS SuperDraft, selectionPoolIncludes, college players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionPoolIncludes Context triple: [2003 MLS SuperDraft, selectionPoolIncludes, college players]
-
A.
selectionIncludes
chosen
Indicates that a chosen set or subset explicitly contains or covers the specified element(s) as part of the selection.
-
B.
selectedWith
Indicates that one entity is chosen or picked in conjunction with, or as part of a set including, another entity.
-
C.
evaluationCriteriaInclude
Indicates that certain criteria are part of, or explicitly included in, the set of standards used to evaluate something.
-
D.
eligibleFrom
Indicates that a subject becomes or is considered eligible starting from a specified point in time or condition.
-
E.
selectedAt
Indicates that an entity was chosen or picked at a specific point in time or under particular selection conditions.
- 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2451e108190a73ccfdc99203d55 |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:53 a.m.