Triple
T2484406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eric Lindros |
E55890
|
entity |
| Predicate | draft position |
P2211
|
FINISHED |
| Object | 1st overall |
—
|
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: 1st overall | Statement: [Eric Lindros, draft position, 1st overall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: draft position Context triple: [Eric Lindros, draft position, 1st overall]
-
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.
draftedInto
Indicates that an entity is formally selected or conscripted to join and serve in a particular organization, group, or role, typically without initiating the choice themselves.
-
D.
draftRound
Indicates the specific round in which an entity was selected during a drafting or selection process.
-
E.
draftedUnderLeader
Indicates that an individual was selected or conscripted into service while a particular leader was in authority or command.
- 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_69ab49e670a88190b928e08302381710 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd20b6d008190acec0eb172e218c9 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b7cf088190bcff4dac6150044c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.