Triple
T36970509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Stockton |
E914551
|
entity |
| Predicate | franchisePlayedFor |
P7425
|
FINISHED |
| Object | Utah Jazz |
—
|
NE NERFINISHED |
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: Utah Jazz | Statement: [John Stockton, franchisePlayedFor, Utah Jazz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: franchisePlayedFor Context triple: [John Stockton, franchisePlayedFor, Utah Jazz]
-
A.
playsForFranchise
chosen
Indicates that one entity is an athlete or performer who is a member of, or competes on behalf of, a particular sports franchise or team.
-
B.
franchiseOfLosingTeam
Indicates that one entity is the franchise to which the losing team in a given game or competition belongs.
-
C.
ownsMajorFranchiseIn
Indicates that an entity has controlling or primary ownership of a major franchise operating within a specified location or jurisdiction.
-
D.
historicalFranchiseOf
Indicates that one entity is or was a franchise (such as a team, branch, or licensed operation) that historically belonged to or operated under another entity.
-
E.
hadFranchise
Indicates that one entity possessed or operated a franchise right or franchise unit of another 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:14 p.m.