Triple
T35928256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spartani |
E1039082
|
entity |
| Predicate | sportLevelContext |
P156222
|
FINISHED |
| Object | professional ice hockey |
—
|
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: professional ice hockey | Statement: [Spartani, sportLevelContext, professional ice hockey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportLevelContext Context triple: [Spartani, sportLevelContext, professional ice hockey]
-
A.
sportsLevel
chosen
Indicates the degree or intensity of involvement, skill, or competitiveness associated with a sport or sporting activity.
-
B.
sportCreated
Indicates that an entity is the originator or inventor of a particular sport.
-
C.
sportsIdentity
Indicates that an entity’s identity, role, or affiliation is defined in the context of sports (e.g., as an athlete, team, or sports-related organization).
-
D.
sportFounded
Indicates that an entity (such as a sports team, club, or organization) was established or created by another entity.
-
E.
sportCategory
Indicates that one entity is classified as a type or category of sport to which the other entity (typically a specific sport or sporting event) belongs.
- 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_69f76e23e4688190a5369138755138bf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.