Triple
T1357663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLB Rule 5 Draft |
E29024
|
entity |
| Predicate | draftOrderPriority |
P2211
|
FINISHED |
| Object | teams with worse records pick earlier |
—
|
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: teams with worse records pick earlier | Statement: [MLB Rule 5 Draft, draftOrderPriority, teams with worse records pick earlier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: draftOrderPriority Context triple: [MLB Rule 5 Draft, draftOrderPriority, teams with worse records pick earlier]
-
A.
orderedBy
Indicates that one entity has placed a request or purchase for another entity, typically specifying who initiated the order.
-
B.
subsequentOrder
Indicates that one order occurs after or follows another order in sequence.
-
C.
orderType
Indicates the specific category or classification of an order, such as its purpose, channel, or processing method.
-
D.
draftPosition
chosen
Indicates the selection order or specific pick at which an entity (such as a player) was chosen in a draft process.
-
E.
headOfOrder
Indicates that one entity holds the primary leadership or highest authority position within a particular order or organized group.
- 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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c28db5048190a279ee9882caaeaf |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef7700c819099b294e8d9320e70 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.