Triple
T2520982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL Scouting Combine |
E55520
|
entity |
| Predicate | evaluationAreas |
P18032
|
FINISHED |
| Object | athleticism |
—
|
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: athleticism | Statement: [NFL Scouting Combine, evaluationAreas, athleticism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evaluationAreas Context triple: [NFL Scouting Combine, evaluationAreas, athleticism]
-
A.
assessmentAreaDefinedBy
chosen
Indicates that the scope or domain of an assessment is specified or delimited by a particular area or boundary.
-
B.
competenceArea
Indicates that one entity has a particular domain, field, or area in which it possesses competence, expertise, or responsibility.
-
C.
keyIssueArea
Indicates that something is a primary topic, domain, or field that is central or especially important within a broader context or discussion.
-
D.
thematicArea
Indicates the subject or item is associated with, or falls under, a particular thematic area or topic of focus.
-
E.
primaryArea
Indicates that one entity is the main or most important area, domain, or field associated with another entity.
- 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_69ab49e4749c8190813311efd1630f1b |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd2367b6c819094239dfd12399643 |
completed | March 7, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69abd0c144b0819092f32a13c1d127e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.