Triple
T10591364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic League of Professional Baseball |
E249996
|
entity |
| Predicate | gameLevel |
P65276
|
FINISHED |
| Object | high-level professional 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: high-level professional baseball | Statement: [Atlantic League of Professional Baseball, gameLevel, high-level professional baseball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameLevel Context triple: [Atlantic League of Professional Baseball, gameLevel, high-level professional baseball]
-
A.
tierOfGame
chosen
Indicates the classification level or rank assigned to a game within a hierarchical system.
-
B.
playedAtLevel
Indicates that an entity participated or performed in an activity, event, or game at a specified level of difficulty, competition, or hierarchy.
-
C.
teamLevel
Indicates the hierarchical rank or tier at which a team operates within an organization, competition, or structure.
-
D.
testingLevel
Indicates the degree or intensity to which something is examined, evaluated, or tested.
-
E.
levels
Indicates that one entity adjusts, equalizes, or smooths out the height, intensity, or degree of another entity.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5277c79808190acc872919eadd126 |
completed | April 7, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69d51907b2b881908ab9a8594688ee06 |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:40 p.m.