Triple
T36828193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Angeles Lakers vs. Philadelphia 76ers (2001 NBA Finals) |
E910065
|
entity |
| Predicate | SixersKeyTeammate |
P2649
|
FINISHED |
| Object | Dikembe Mutombo |
—
|
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: Dikembe Mutombo | Statement: [Los Angeles Lakers vs. Philadelphia 76ers (2001 NBA Finals), SixersKeyTeammate, Dikembe Mutombo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SixersKeyTeammate Context triple: [Los Angeles Lakers vs. Philadelphia 76ers (2001 NBA Finals), SixersKeyTeammate, Dikembe Mutombo]
-
A.
76ersKeyPlayer
Indicates that the subject is a primary or especially important player for the Philadelphia 76ers basketball team.
-
B.
wasTeammateOf
Indicates that two entities were members of the same team during an overlapping period of time.
-
C.
SixersHomeArena
Indicates that the specified arena is the home arena of the Philadelphia 76ers basketball team.
-
D.
notableTeammate
chosen
Indicates that one entity has a teammate relationship with another entity who is particularly prominent, distinguished, or noteworthy.
-
E.
teammateAtHouston
Indicates that two individuals were teammates while playing for a team based in Houston.
- 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_69f76e7e9d60819092442fba73290a46 |
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:13 p.m.