Triple
T260747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wes Welker |
E5534
|
entity |
| Predicate | coachingPosition |
P3459
|
FINISHED |
| Object | wide receivers coach |
—
|
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: wide receivers coach | Statement: [Wes Welker, coachingPosition, wide receivers coach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coachingPosition Context triple: [Wes Welker, coachingPosition, wide receivers coach]
-
A.
championCoachPosition
Indicates that a coach held the coaching position for a team that won a championship.
-
B.
coachOf
Indicates that one entity serves as the coach (trainer or manager) of another entity, typically a person or team.
-
C.
leadershipPosition
chosen
Indicates that one entity holds a role of authority, guidance, or decision-making responsibility over others within an organization, group, or context.
-
D.
playerCoachTeam
Indicates a relationship where a player is coached by a specific coach while playing for a particular team.
-
E.
notableCoach
Indicates that one entity is a coach who is widely recognized or distinguished in relation to the other 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b6c968c819094fc903a3a377e15 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.