Triple
T3939684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlotte Hornets |
E92003
|
entity |
| Predicate | expansionSuccessorFounded |
P52680
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [Charlotte Hornets, expansionSuccessorFounded, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionSuccessorFounded Context triple: [Charlotte Hornets, expansionSuccessorFounded, 2004]
-
A.
successorDeterminedBy
Indicates that the identity of a successor is established or chosen according to a specified rule, process, or determining factor.
-
B.
successorConfiguration
Indicates that one configuration directly follows another as its immediate next state in a sequence or process.
-
C.
eventualSuccessor
Indicates that one entity will become the successor of another at some later point in time, rather than immediately.
-
D.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
E.
successorState
Indicates that one state directly follows another as the immediate next state in a sequence or process.
- 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_69aed965502c8190904ebad1203a4ae8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeedfb12b88190a6ca6574b1aadb6e |
completed | March 9, 2026, 3:57 p.m. |
| PD | Predicate disambiguation | batch_69aee7625ad4819097e4e8a168c19274 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeed3260cc8190bf294bdab507b1f9 |
completed | March 9, 2026, 3:54 p.m. |
Created at: March 9, 2026, 3:24 p.m.