Triple
T8382346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World All-Stars |
E197721
|
entity |
| Predicate | rosterBasis |
P81764
|
FINISHED |
| Object | individual player performance in NHL |
—
|
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: individual player performance in NHL | Statement: [World All-Stars, rosterBasis, individual player performance in NHL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rosterBasis Context triple: [World All-Stars, rosterBasis, individual player performance in NHL]
-
A.
typicalRosterSource
Indicates that one entity is the usual or standard source from which the other entity’s roster or list of members is derived.
-
B.
rosterRequirement
Indicates that one entity specifies or imposes a required composition, number, or type of participants that must be included in another entity’s roster.
-
C.
rosterSize
Indicates the total number of individuals included on a given roster.
-
D.
notableMemberOfRoster
Indicates that an entity is a distinguished or prominent member within a particular roster or lineup.
-
E.
rosterTurnover
Indicates a change in the members of a group or team, such as additions, removals, or replacements within its roster.
- 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.