Triple
T12513748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBSC Baseball World Rankings |
E299144
|
entity |
| Predicate | rankingTarget |
P59486
|
FINISHED |
| Object | men's baseball national teams |
—
|
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: men's baseball national teams | Statement: [WBSC Baseball World Rankings, rankingTarget, men's baseball national teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingTarget Context triple: [WBSC Baseball World Rankings, rankingTarget, men's baseball national teams]
-
A.
rankingScope
chosen
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
B.
rankingBehind
Indicates that one entity holds a lower or later position than another in an ordered ranking or hierarchy.
-
C.
rankingType
Indicates the specific basis or method by which items are ordered or ranked relative to one another.
-
D.
rankingBasis
Indicates the criterion or standard used to determine the order or rank of entities in a ranking.
-
E.
peakRanking
Indicates the highest position or rank an entity has ever achieved within a specified ranking system or context.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.