Triple
T23486483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lou Little |
E570546
|
entity |
| Predicate | coachedYearsAtGeorgetown |
P15414
|
FINISHED |
| Object | 1924–1929 |
—
|
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: 1924–1929 | Statement: [Lou Little, coachedYearsAtGeorgetown, 1924–1929]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coachedYearsAtGeorgetown Context triple: [Lou Little, coachedYearsAtGeorgetown, 1924–1929]
-
A.
hasCoachedFor
Indicates that one entity has served in a coaching role for another entity, such as a team, organization, or individual.
-
B.
playedCollegeYears
Indicates the span of years during which an entity participated in college-level play (e.g., as a student-athlete).
-
C.
numberOfSeasonsCoachedAtBostonUniversity
Indicates the number of seasons an individual has served as a coach at Boston University.
-
D.
yearsActiveAsCoach
chosen
Indicates the span of time, typically in years, during which an individual has served in a coaching role.
-
E.
coachedAthletesAt
Indicates a relationship where a coach has trained or instructed athletes at a particular organization, team, or location.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a754825481909b005ca5654c3159 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:04 p.m.