Triple
T13213676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Jackson |
E314553
|
entity |
| Predicate | hasPlayedForMultipleTeams |
P2170
|
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: [Mark Jackson, hasPlayedForMultipleTeams, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayedForMultipleTeams Context triple: [Mark Jackson, hasPlayedForMultipleTeams, true]
-
A.
hasFormerTeam
Indicates that an entity was previously a member of, played for, or was affiliated with a team in the past but is no longer associated with that team.
-
B.
memberTeamAtVariousTimes
Indicates that an entity has been a member of a particular team during one or more distinct time periods.
-
C.
playedFor
chosen
Indicates that one entity has been a member of or participated as a player for a particular team, organization, or group.
-
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.
leagueParticipatedInAsPlayer
Indicates that a person, in the role of a player, took part in competitions organized by a specific league.
- 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:17 p.m.