Triple
T7589422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monterrey Sultanes |
E179696
|
entity |
| Predicate | isSuccessfulFranchise |
P78015
|
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: [Monterrey Sultanes, isSuccessfulFranchise, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSuccessfulFranchise Context triple: [Monterrey Sultanes, isSuccessfulFranchise, true]
-
A.
franchiseStatus
Indicates the current standing or condition of a franchise relationship between parties, such as whether it is active, inactive, pending, or terminated.
-
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.
operatesUnderFranchiseFrom
Indicates that one entity conducts its business or operations under the franchising rights, brand, and system granted by another entity.
-
D.
distributesFranchise
Indicates that one party grants or allocates franchise rights or opportunities to another party.
-
E.
hadFranchise
Indicates that one entity possessed or operated a franchise right or franchise unit of another entity.
- 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_69c69f335248819093c1006f30513708 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f99991948190af1fb0635895ad94 |
completed | March 27, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e04c2c8190a889d928515d9b8e |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8184bb08190b2f70545a6aa277c |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:52 p.m.