Triple
T12787204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stinger |
E305661
|
entity |
| Predicate | associatedSportLevel |
P24551
|
FINISHED |
| Object | professional sports |
—
|
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 sports | Statement: [Stinger, associatedSportLevel, professional sports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedSportLevel Context triple: [Stinger, associatedSportLevel, professional sports]
-
A.
associatedLeagueLevel
Indicates that one entity is linked to another entity representing the competitive tier or level of a sports league.
-
B.
governsSportLevel
Indicates that one entity has authority to set, control, or regulate the competitive level or tier at which a sport or sporting activity is conducted.
-
C.
representsSportLevel
chosen
Indicates that an entity participates in or is associated with a particular level or tier within a sport.
-
D.
athleticAssociationTier
Indicates the competitive level or division within an athletic association to which an entity (such as a team or institution) belongs.
-
E.
relatedSport
Indicates that there is an association or connection between an entity and a particular sport.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e5dbdb88190a1b06721ada51627 |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:29 p.m.