Triple
T21448286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Carrier |
E529134
|
entity |
| Predicate | positionInDraft |
P2211
|
FINISHED |
| Object | first-round draft pick |
—
|
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: first-round draft pick | Statement: [Mark Carrier, positionInDraft, first-round draft pick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInDraft Context triple: [Mark Carrier, positionInDraft, first-round draft pick]
-
A.
draftPosition
chosen
Indicates the selection order or specific pick at which an entity (such as a player) was chosen in a draft process.
-
B.
draftedIn
Indicates that one entity was selected or recruited into another entity (such as a team, organization, or military service) through a formal draft process.
-
C.
draftedAt
Indicates that an entity was selected or chosen by another entity at a specific draft event or position.
-
D.
draftedInPeriod
Indicates that an entity was formally drafted or selected during a specified time period.
-
E.
positionInPlan
Indicates the specific place or ordering of an element within a larger plan or sequence of planned steps.
- 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_69e0c457579481909db68053ed99750c |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9d04548819086594c20faa5217d |
completed | April 23, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:06 p.m.