Triple
T2367330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Industriales |
E46011
|
entity |
| Predicate | countryLeagueContext |
P14340
|
FINISHED |
| Object | top-tier Cuban 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: top-tier Cuban baseball | Statement: [Industriales, countryLeagueContext, top-tier Cuban baseball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryLeagueContext Context triple: [Industriales, countryLeagueContext, top-tier Cuban baseball]
-
A.
countryLeagueSystem
chosen
Indicates that a particular league system operates within, or is associated with, a specific country.
-
B.
leagueContext
Indicates the broader league or competition setting within which the relationship or action takes place.
-
C.
league2
Indicates that an entity participates in, is a member of, or is otherwise affiliated with a specific sports league or competitive organization.
-
D.
regionLeague
Indicates a relationship where a specific region is associated with, belongs to, or is governed by a particular league or league-level organization.
-
E.
stateLeague
Indicates that a sports team or club competes in, or is affiliated with, a particular state-level league or competition.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc74b6bdc8190a12b2bcaa2dd7616 |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc59b88348190a2d6c08f69974117 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:56 p.m.