Triple
T1099860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santiago de Cuba |
E24352
|
entity |
| Predicate | mainSport |
P1080
|
FINISHED |
| Object | baseball |
—
|
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: baseball | Statement: [Santiago de Cuba, mainSport, baseball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainSport Context triple: [Santiago de Cuba, mainSport, baseball]
-
A.
primarySport
chosen
Indicates the main sport with which an entity (such as a person, team, or organization) is most closely associated or primarily involved.
-
B.
popularSport
Indicates that a sport is widely liked, followed, or played by many people within a certain group or region.
-
C.
sportFocus
Indicates that one entity has a primary emphasis, specialization, or concentration on a particular sport represented by the other entity.
-
D.
sportCategory
Indicates that one entity is classified as a type or category of sport to which the other entity (typically a specific sport or sporting event) belongs.
-
E.
traditionalSport
Indicates that an entity is a sport practiced within a culture or community that has been passed down over generations and is recognized as part of traditional or heritage activities.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9be92688190838ce35cd67e01f3 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b745ef3481909a7ce4647c8567b3 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:43 p.m.