Triple
T6806769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland Bronchos |
E156325
|
entity |
| Predicate | usedByFranchise |
P73117
|
FINISHED |
| Object | Cleveland American League franchise |
—
|
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: Cleveland American League franchise | Statement: [Cleveland Bronchos, usedByFranchise, Cleveland American League franchise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByFranchise Context triple: [Cleveland Bronchos, usedByFranchise, Cleveland American League franchise]
-
A.
franchiseOf
Indicates that one entity operates as a franchise belonging to or licensed by another entity.
-
B.
franchiseWorkedOn
Indicates that an entity has contributed work to, or been professionally involved with, a particular franchise.
-
C.
includedFranchise
Indicates that one franchise is contained within, or forms part of, another franchise.
-
D.
partOfFranchiseLineage
Indicates that one entity belongs to, or is derived from, the same overarching franchise lineage as another entity, reflecting continuity within a shared franchise.
-
E.
associatedFranchise
Indicates a relationship where one entity is linked to, or belongs within, a particular franchise or franchise universe.
- 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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d30a006081908996e31aa7ced0ac |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d2a8f9188190abbb8c730e7b5edf |
completed | March 27, 2026, 6:55 p.m. |
Created at: March 27, 2026, 2:16 p.m.