Triple
T443153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International League |
E10156
|
entity |
| Predicate | umpiresProvidedBy |
P13248
|
FINISHED |
| Object | professional umpire staff |
—
|
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 umpire staff | Statement: [International League, umpiresProvidedBy, professional umpire staff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: umpiresProvidedBy Context triple: [International League, umpiresProvidedBy, professional umpire staff]
-
A.
umpires
Indicates that an entity serves as the umpire overseeing, judging, or officiating an event, activity, or interaction involving another entity.
-
B.
umpireCrewSize
Indicates the number of umpires assigned to work together as a crew for a particular game or event.
-
C.
umpireCrewChief
Indicates that one entity serves as the crew chief (lead umpire) for a particular umpire crew.
-
D.
numberOfJudges
Indicates the total count of judges associated with a particular case, event, or entity.
-
E.
hasChiefJudge
Indicates that an entity holds the role or position of chief judge for another entity (such as a court or judicial body).
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef43e8f88190a5d368add11a38c0 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2edde2b9c8190bd20b582eb4c5065 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeb9e6b0819093863959a6e5730a |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.