Triple
T25647554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Legion Baseball teams |
E643005
|
entity |
| Predicate | primaryPlayerGroup |
P189412
|
FINISHED |
| Object | high school–age players |
—
|
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: high school–age players | Statement: [American Legion Baseball teams, primaryPlayerGroup, high school–age players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPlayerGroup Context triple: [American Legion Baseball teams, primaryPlayerGroup, high school–age players]
-
A.
primaryUserGroup
Indicates the main or default user group to which a user is primarily assigned or associated.
-
B.
primaryClientGroup
Indicates the main group of clients that an entity primarily serves or is chiefly associated with.
-
C.
primaryTeam
Indicates that one entity is the main or principal team associated with another entity, such as a person, project, or organization.
-
D.
primaryUserGroups
Indicates the main or default user groups to which an entity (such as a user account) is assigned.
-
E.
primaryPlayerSource
Indicates that an entity serves as the main origin or provider of a player within a given context or system.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: April 21, 2026, 5:56 p.m.