Triple
T11979843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston Bolts |
E285128
|
entity |
| Predicate | hasYouthTeamsIn |
P80774
|
FINISHED |
| Object | elite youth leagues |
—
|
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: elite youth leagues | Statement: [Boston Bolts, hasYouthTeamsIn, elite youth leagues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYouthTeamsIn Context triple: [Boston Bolts, hasYouthTeamsIn, elite youth leagues]
-
A.
hasYouthTeam
Indicates that an entity has an associated youth team that serves as its junior or developmental squad.
-
B.
hasAdultTeams
Indicates that the subject is associated with one or more teams composed of adult participants.
-
C.
includesYouthLeagues
chosen
Indicates that the subject entity offers, contains, or is associated with organized leagues or programs specifically for youth participants.
-
D.
playedForJuniorTeam
Indicates that an individual was a member of and played for a specific junior-level sports team.
-
E.
hasYouthProgram
Indicates that an entity offers or is associated with an organized program or set of activities specifically designed for young people.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903acbb9081908fe7f8360057785c |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.