Triple
T9023124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cris Carter |
E215975
|
entity |
| Predicate | positionPlayedForTeam |
P85904
|
FINISHED |
| Object | wide receiver for Minnesota Vikings |
—
|
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 receiver for Minnesota Vikings | Statement: [Cris Carter, positionPlayedForTeam, wide receiver for Minnesota Vikings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionPlayedForTeam Context triple: [Cris Carter, positionPlayedForTeam, wide receiver for Minnesota Vikings]
-
A.
teamPlayedFor
Indicates that a person was a member of and played for a particular sports team.
-
B.
playedFor
Indicates that one entity has been a member of or participated as a player for a particular team, organization, or group.
-
C.
playedForTeamEnd
Indicates that an entity’s period of playing for a particular team ended at a specified time or event.
-
D.
laterPlayedFor
Indicates that an individual was a member of or played for a team or organization at a time after a previously referenced team or organization.
-
E.
memberOfSportsTeamAsPlayer
Indicates that a person participates as a player on a specific sports team.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7a770081908dfe3ce3374a04ba |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f887108819096d45a186fc137b3 |
completed | March 31, 2026, 11:58 p.m. |
Created at: March 30, 2026, 7:07 p.m.