Triple
T24357447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Hornets |
E613961
|
entity |
| Predicate | preNFLStatus |
P155909
|
FINISHED |
| Object | non-NFL major league team |
—
|
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: non-NFL major league team | Statement: [Chicago Hornets, preNFLStatus, non-NFL major league team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preNFLStatus Context triple: [Chicago Hornets, preNFLStatus, non-NFL major league team]
-
A.
NFLStatus
Indicates the current professional status or condition of an entity within the context of the National Football League (e.g., active, injured, retired, free agent).
-
B.
NFLDraftStatus
Indicates the relationship between a player and their status in the NFL draft, such as whether, when, and how they were selected.
-
C.
nflTeamState
Indicates the U.S. state in which an NFL team is based or associated.
-
D.
nflRetirementStatus
Indicates the retirement state of an NFL player, such as whether they are currently active, retired, or in another defined career status.
-
E.
joinedNFL
Indicates that an entity became a member of, or started playing in, the National Football League (NFL).
- 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29349ee188190a9d54b2c725b8a27 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2 a.m.