Triple
T9902829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2002 MLS SuperDraft |
E182326
|
entity |
| Predicate | hasDraftClass |
P91078
|
FINISHED |
| Object | 2002 MLS rookie class |
—
|
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: 2002 MLS rookie class | Statement: [2002 MLS SuperDraft, hasDraftClass, 2002 MLS rookie class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDraftClass Context triple: [2002 MLS SuperDraft, hasDraftClass, 2002 MLS rookie class]
-
A.
hasDraft
Indicates that one entity possesses or is associated with a preliminary or unfinished version of another entity.
-
B.
hasDraftRelationshipWith
Indicates a provisional or not-yet-finalized relationship exists between two entities.
-
C.
hasDraftOrAssignmentSystem
Indicates that an entity possesses or is associated with a system for managing drafts or assignments.
-
D.
hasDocumentClass
Indicates that an entity is associated with, or categorized under, a specific class or type of document.
-
E.
usesDraftSystem
Indicates that one entity employs or operates using a draft-based system or mechanism rather than a finalized or direct method.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4e391888190a3f5e5a1bf1cf9ff |
completed | April 2, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69cd1d8c584081908b73de75eb18e438 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd3581a9688190a00cef4c3eebb0ae |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:40 p.m.