Triple
T15524849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asian Baseball Championship |
E369055
|
entity |
| Predicate | scopeOfTeams |
P119026
|
FINISHED |
| Object | top national baseball teams in Asia |
—
|
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 national baseball teams in Asia | Statement: [Asian Baseball Championship, scopeOfTeams, top national baseball teams in Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeOfTeams Context triple: [Asian Baseball Championship, scopeOfTeams, top national baseball teams in Asia]
-
A.
coversTeam
Indicates that one entity provides reporting, media coverage, or journalistic attention to a specific team.
-
B.
regionTeam
Indicates that a team is associated with, operates in, or represents a specific geographic region.
-
C.
clubScope
Indicates that something is within the organizational, functional, or contextual scope of a particular club.
-
D.
coreTeams
Indicates that the entities are part of the same primary or central team within an organization or project.
-
E.
collaborationScope
Indicates the extent, boundaries, and areas of responsibility covered by a particular collaboration between entities.
- F. None of above. chosen
Provenance (4 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e04145178481909fb0339a79d4239e |
completed | April 16, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_69ded28ab0588190a47a9090d1238707 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57165288190979b7acb71ad5145 |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 4:05 a.m.