Triple
T3606919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinston, North Carolina |
E76394
|
entity |
| Predicate | hasBasketballTradition |
P19423
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kinston, North Carolina, hasBasketballTradition, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBasketballTradition Context triple: [Kinston, North Carolina, hasBasketballTradition, true]
-
A.
hasNBAFranchiseHistoryFrom
Indicates that an entity has a history of operating an NBA franchise originating from a specified location or organization.
-
B.
hasBasketballLevel
Indicates that an entity possesses a specified level of skill, proficiency, or ranking in basketball.
-
C.
hasBasketballTournament
Indicates that a basketball tournament is organized, hosted, or associated with a particular entity or context.
-
D.
hasWinningTradition
Indicates that an entity (such as a team or organization) is characterized by a consistent history of success or victories in its competitive activities.
-
E.
hasTraditionIn
chosen
Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
- 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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc1e33cfc8190afc716b19480fbce |
completed | March 8, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69adb83d8b1c8190b3bddbc5dc995a87 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.