Triple
T22287787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tucson Toros |
E550909
|
entity |
| Predicate | operatedAsPCLFranchiseUntil |
P147699
|
FINISHED |
| Object | 1997 |
—
|
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: 1997 | Statement: [Tucson Toros, operatedAsPCLFranchiseUntil, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedAsPCLFranchiseUntil Context triple: [Tucson Toros, operatedAsPCLFranchiseUntil, 1997]
-
A.
operatesUnderFranchiseFrom
Indicates that one entity conducts its business or operations under the franchising rights, brand, and system granted by another entity.
-
B.
establishedAsFranchise
Indicates that an entity has been set up or designated to operate as a franchise under a broader brand or business system.
-
C.
hadFranchiseSystem
Indicates that an entity operated under or possessed a particular franchise business system or model.
-
D.
maintainedFranchiseFor
Indicates that one entity was responsible for operating, managing, or upholding a franchise on behalf of another entity over a period of time.
-
E.
subfranchiseOf
Indicates that one franchise operates as a subordinate or derivative franchise under the authority or umbrella of another franchise.
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1560896348190985725ac8ad406b3 |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:40 p.m.