Triple
T1916346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luc Longley |
E40025
|
entity |
| Predicate | NBAdraftPickNumber |
P33128
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [Luc Longley, NBAdraftPickNumber, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NBAdraftPickNumber Context triple: [Luc Longley, NBAdraftPickNumber, 7]
-
A.
NFLDraftPickNumber
Indicates the specific overall selection position at which an individual was chosen in an NFL Draft.
-
B.
draftedUnder
Indicates that one entity was formally selected or conscripted into a role, position, or service according to the authority, rules, or jurisdiction of another entity.
-
C.
draftedAt
Indicates that an entity was selected or chosen by another entity at a specific draft event or position.
-
D.
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.
-
E.
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.
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb20f54848190b9457e1231aa49db |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafed2ab481908920334e77b1021b |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb1b180e481908bbe893d6ba6208b |
completed | March 7, 2026, 5:03 a.m. |
Created at: March 4, 2026, 7:35 p.m.