Triple
T2020601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas–New York |
E44094
|
entity |
| Predicate | hasSportsLevel |
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: [Texas–New York, hasSportsLevel, professional sports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSportsLevel Context triple: [Texas–New York, hasSportsLevel, professional sports]
-
A.
hasSportsStatus
Indicates that an entity holds a particular sports-related status, role, or classification (such as amateur, professional, active, or retired) within a sporting context.
-
B.
representsSportLevel
chosen
Indicates that an entity participates in or is associated with a particular level or tier within a sport.
-
C.
hasBasketballLevel
Indicates that an entity possesses a specified level of skill, proficiency, or ranking in basketball.
-
D.
includesSport
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
-
E.
hasSportsBody
Indicates that an entity possesses a body or physique that is characteristic of someone who regularly engages in sports or athletic activities.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8d0bcbc8190bbbb726ecae1c51b |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a389408190a84a54856352f15b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.