Triple
T7425068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Crabtree |
E171346
|
entity |
| Predicate | playedForTeamInYears |
P2170
|
FINISHED |
| Object | San Francisco 49ers 2009–2014 |
—
|
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: San Francisco 49ers 2009–2014 | Statement: [Michael Crabtree, playedForTeamInYears, San Francisco 49ers 2009–2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedForTeamInYears Context triple: [Michael Crabtree, playedForTeamInYears, San Francisco 49ers 2009–2014]
-
A.
careerSpanTeam
Indicates the team for which an individual’s entire career span (or a defined portion of it) is being measured or associated.
-
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.
nationalTeamYears
Indicates the span of years during which an entity was active as a member of a national team.
-
E.
winnerCareerSpanTeam
Indicates the team for which a winner competed during the span of their professional career.
- 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f302b33481908eae877970f2bbdf |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:12 p.m.