Triple
T26839544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexican League |
E675738
|
entity |
| Predicate | usesDraft |
P57037
|
FINISHED |
| Object | no traditional amateur draft system |
—
|
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: no traditional amateur draft system | Statement: [Mexican League, usesDraft, no traditional amateur draft system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDraft Context triple: [Mexican League, usesDraft, no traditional amateur draft system]
-
A.
usesDraftSystem
chosen
Indicates that one entity employs or operates using a draft-based system or mechanism rather than a finalized or direct method.
-
B.
hasDraft
Indicates that one entity possesses or is associated with a preliminary or unfinished version of another entity.
-
C.
supportsDrafts
Indicates that an entity is capable of handling, saving, or working with draft versions of items before they are finalized.
-
D.
draft_m
Indicates that an entity is involved in creating, editing, or preparing a preliminary or non-final version of another entity.
-
E.
hasDraftRelationshipWith
Indicates a provisional or not-yet-finalized relationship exists between two entities.
- 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:07 a.m.