Triple
T16215610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilly Holbrook |
E393584
|
entity |
| Predicate | roleInJuniorLeague |
P74878
|
FINISHED |
| Object | leader |
—
|
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: leader | Statement: [Hilly Holbrook, roleInJuniorLeague, leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInJuniorLeague Context triple: [Hilly Holbrook, roleInJuniorLeague, leader]
-
A.
roleInClub
chosen
Indicates that an entity holds a specific position or function within a particular club.
-
B.
playedForJuniorTeam
Indicates that an individual was a member of and played for a specific junior-level sports team.
-
C.
developmentLeagueFor
Indicates that one entity serves as a developmental or minor league affiliate for another, typically higher-level, sports team or organization.
-
D.
representsInJuniorCategory
Indicates that an entity serves as a representative or participant in a junior-level category within a given context or organization.
-
E.
includesYouthLeagues
Indicates that the subject entity offers, contains, or is associated with organized leagues or programs specifically for youth participants.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e227f4685c8190aa1e9304e4a62d13 |
completed | April 17, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.