Triple
T19497920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese Professional Baseball League |
E487820
|
entity |
| Predicate | hasUmpireCrew |
P95752
|
FINISHED |
| Object | professional umpires |
—
|
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: professional umpires | Statement: [Chinese Professional Baseball League, hasUmpireCrew, professional umpires]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUmpireCrew Context triple: [Chinese Professional Baseball League, hasUmpireCrew, professional umpires]
-
A.
hasOfficiatingCrew
chosen
Indicates that an event, typically a sports game or formal proceeding, is assigned a specific group of officials responsible for overseeing and enforcing its rules.
-
B.
umpireCrewSize
Indicates the number of umpires assigned to work together as a crew for a particular game or event.
-
C.
umpireCrewRole
Indicates the specific role or position an umpire holds within an umpire crew during an event or game.
-
D.
umpireCrewChief
Indicates that one entity serves as the crew chief (lead umpire) for a particular umpire crew.
-
E.
typeOfUmpire
Indicates the specific category or role an umpire belongs to within the broader set of umpires.
- 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63493232881909fc33fb84da3e1b5 |
completed | April 20, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7bd25881908caa04eaef1f6718 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:40 p.m.