Triple
T779382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlotte Hornets |
E16461
|
entity |
| Predicate | conferenceTitleCount |
P19825
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [Charlotte Hornets, conferenceTitleCount, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceTitleCount Context triple: [Charlotte Hornets, conferenceTitleCount, 0]
-
A.
conferenceTitles
Indicates a relationship where one entity (such as a conference event or series) is associated with the titles under which it is or has been held.
-
B.
conferenceCounterpart
Indicates that two entities are corresponding participants or roles in the same conference or meeting, positioned as counterparts to each other.
-
C.
conferenceAtTheTime
Indicates that an event or situation occurs during the time period in which a specified conference is taking place.
-
D.
conferenceLevel
Indicates the competitive or organizational tier at which a conference or event is classified or held.
-
E.
conferenceType
Indicates the specific category or kind of conference associated with an entity (e.g., workshop, symposium, seminar).
- 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_69a4936ad1fc81908f190208059ccf78 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a90365648190ace53b0f0e87aa68 |
completed | March 1, 2026, 9 p.m. |
| PD | Predicate disambiguation | batch_69a4a50bd23081908908235b8ec9201e |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a8f09d108190b8c83a6169d65c0c |
completed | March 1, 2026, 9 p.m. |
Created at: March 1, 2026, 7:37 p.m.