Triple
T1167773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julian Edelman |
E24837
|
entity |
| Predicate | playedQuarterbackInCollege |
P7105
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Julian Edelman, playedQuarterbackInCollege, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedQuarterbackInCollege Context triple: [Julian Edelman, playedQuarterbackInCollege, true]
-
A.
playedCollegeTeam
Indicates that an athlete was a member of and competed for a particular college sports team.
-
B.
playedWithQuarterback
Indicates that one player participated on the same team at the same time as a specific quarterback, sharing game or practice play together.
-
C.
positionPlayedInCollege
chosen
Indicates the specific playing position an individual held on a sports team during their college career.
-
D.
notableFormerQuarterback
Indicates that the subject was previously a quarterback and is recognized as notable or distinguished in that former role.
-
E.
quarterback
Indicates that an entity performs the role or action of playing as the quarterback in a football context for another entity (such as a team).
- 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bccef84481908864e819884af86c |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb548c1481909092626c572d8782 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.