Triple
T23950105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston Celtics vs Detroit Pistons |
E603022
|
entity |
| Predicate | featuredStarPlayer |
P42751
|
FINISHED |
| Object | Larry Bird |
—
|
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: Larry Bird | Statement: [Boston Celtics vs Detroit Pistons, featuredStarPlayer, Larry Bird]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredStarPlayer Context triple: [Boston Celtics vs Detroit Pistons, featuredStarPlayer, Larry Bird]
-
A.
starredActor
Indicates that an actor performed a leading or significant role in a particular production or work.
-
B.
featuresPlayer
chosen
Indicates that something includes or prominently presents a particular player as part of its content or composition.
-
C.
featuresPlayers
Indicates that something includes or showcases one or more players as part of its content or composition.
-
D.
supportsStarPlayers
Indicates that one entity provides assistance, resources, or backing specifically to star or top-performing players.
-
E.
opposingStarPlayer
Indicates that one player is the primary or notable player on the opposing team relative to another player or team.
- 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d03140f08190b4356626628ff56f |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:19 p.m.