Triple
T33046329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olmecas de Tabasco |
E845605
|
entity |
| Predicate | typeOfBaseball |
P3186
|
FINISHED |
| Object | summer league 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: summer league baseball | Statement: [Olmecas de Tabasco, typeOfBaseball, summer league baseball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfBaseball Context triple: [Olmecas de Tabasco, typeOfBaseball, summer league baseball]
-
A.
battedBallType
Indicates the specific kind of contact or trajectory resulting when a ball is hit (e.g., ground ball, fly ball, line drive).
-
B.
playsBaseballFor
Indicates that one entity participates as a baseball player on the team or organization represented by the other entity.
-
C.
ballType
chosen
Indicates the specific category or kind of ball associated with an entity.
-
D.
capacityBaseball
Indicates the maximum number of spectators that a baseball venue is designed or allowed to hold.
-
E.
ballparkClass
Indicates that two values or quantities are approximately equal within a rough or acceptable range, rather than being exactly the same.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a008ebb22408190a2293bced40a7e53 |
completed | May 10, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_6a008e8715dc8190ab23292605901bf4 |
completed | May 10, 2026, 1:56 p.m. |
Created at: May 1, 2026, 1:24 a.m.