Triple
T441886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL Draft |
E10130
|
entity |
| Predicate | preDraftProcess |
P13214
|
FINISHED |
| Object | player evaluation by NFL teams |
—
|
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: player evaluation by NFL teams | Statement: [NFL Draft, preDraftProcess, player evaluation by NFL teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preDraftProcess Context triple: [NFL Draft, preDraftProcess, player evaluation by NFL teams]
-
A.
draft
Indicates that one entity prepares an initial or preliminary version of something, typically a document, plan, or design, which may be revised later.
-
B.
draftingStarted
Indicates that the process of creating an initial version or draft of something has begun.
-
C.
pretext
Indicates that one party uses a stated reason or excuse to conceal their true motive for an action or decision.
-
D.
hasDraft
Indicates that one entity possesses or is associated with a preliminary or unfinished version of another entity.
-
E.
draftedBy
Indicates that something (such as a document, plan, or version) was created or written in its initial form by a particular agent or author.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef42b4008190abed9d79926c7022 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2edde2b9c8190bd20b582eb4c5065 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeb9e6b0819093863959a6e5730a |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.