Triple
T443142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International League |
E10156
|
entity |
| Predicate | talentPipelineFor |
P4674
|
FINISHED |
| Object | Major League Baseball clubs |
—
|
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: Major League Baseball clubs | Statement: [International League, talentPipelineFor, Major League Baseball clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: talentPipelineFor Context triple: [International League, talentPipelineFor, Major League Baseball clubs]
-
A.
recruitingProfile
Indicates that an entity serves as or is associated with a recruiting profile used for hiring or talent acquisition activities.
-
B.
recruitmentFrom
Indicates that one entity recruits or sources members, employees, or participants from another entity.
-
C.
peakPersonnel
Indicates the maximum number of personnel involved or present at any point during a specified period or activity.
-
D.
targetOfficeSought
Indicates the specific public or organizational office or position that an individual is seeking or running for.
-
E.
recruitmentBase
chosen
Indicates the foundational source, location, or context from which recruitment efforts or recruited entities originate.
- 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_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. |
Created at: Feb. 28, 2026, 1:11 p.m.