Triple
T3797222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iowa Barnstormers |
E91600
|
entity |
| Predicate | notablePlayerPosition |
P11751
|
FINISHED |
| Object | quarterback |
—
|
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: quarterback | Statement: [Iowa Barnstormers, notablePlayerPosition, quarterback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlayerPosition Context triple: [Iowa Barnstormers, notablePlayerPosition, quarterback]
-
A.
playsInPosition
chosen
Indicates that an entity (typically a player) performs or operates in a specific role or position within a game, sport, or activity.
-
B.
clubPosition
Indicates the specific role or position an individual holds within a sports club or team.
-
C.
notableCornerback
Indicates that the subject is recognized as an especially distinguished or prominent cornerback in American football.
-
D.
hasNotablePosition
Indicates that an entity holds or has held a position, role, or office considered notable or significant.
-
E.
positionInLineup
Indicates the specific ordered place an entity occupies within a lineup or sequence of entities.
- 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_69aed96354f48190a768966d6bd19b04 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecefa3608190a7a20ed6df6a64b2 |
completed | March 9, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69aee743c8d08190a9f9c97b836bd703 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.