Triple
T27670901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Converge FiberXers |
E697659
|
entity |
| Predicate | foundedAsPbaFranchise |
P46462
|
FINISHED |
| Object | 2022 |
—
|
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: 2022 | Statement: [Converge FiberXers, foundedAsPbaFranchise, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsPbaFranchise Context triple: [Converge FiberXers, foundedAsPbaFranchise, 2022]
-
A.
foundedFranchise
Indicates that an entity established or created a particular franchise.
-
B.
foundedAsFranchiseYear
chosen
Indicates the year in which an entity was established specifically as a franchise.
-
C.
establishedAsCurrentFranchise
Indicates that an entity has been formally designated or recognized as the current active franchise for another entity.
-
D.
hasNBAFranchiseHistoryFrom
Indicates that an entity has a history of operating an NBA franchise originating from a specified location or organization.
-
E.
historicalFranchiseOf
Indicates that one entity is or was a franchise (such as a team, branch, or licensed operation) that historically belonged to or operated under another entity.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 27, 2026, 2:41 p.m.