Triple
T8382339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World All-Stars |
E197721
|
entity |
| Predicate | playerAffiliation |
P81763
|
FINISHED |
| Object | players under NHL contract |
—
|
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: players under NHL contract | Statement: [World All-Stars, playerAffiliation, players under NHL contract]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerAffiliation Context triple: [World All-Stars, playerAffiliation, players under NHL contract]
-
A.
leagueAffiliationThroughOwnedTeam
Indicates that an entity is affiliated with a league by virtue of owning a team that participates in that league.
-
B.
teamAffiliationStructure
Indicates the organizational relationship that defines how a team is structured, including its internal roles, hierarchy, and affiliations.
-
C.
leagueAffiliationManaged
Indicates that one entity manages, oversees, or administers the league affiliation of another entity.
-
D.
stateTeamOf
Indicates that one entity is the official team representing a particular state associated with another entity.
-
E.
roleAtSportsTeam
Indicates the specific position or function an individual holds within a sports team.
- F. None of above. chosen
Provenance (4 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_69ca82f64c188190af4e1608036b865d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80ddc0f08190a90d4d9070bf713b |
completed | March 31, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69cb70cfe82881909fe374ba52649e84 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76da264881909483b835e1db06da |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 6:02 p.m.