Triple
T2587774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgetown Hoyas men's basketball |
E58045
|
entity |
| Predicate | coachTenureOfJohnThompsonJr |
P11639
|
FINISHED |
| Object | 1972–1999 |
—
|
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: 1972–1999 | Statement: [Georgetown Hoyas men's basketball, coachTenureOfJohnThompsonJr, 1972–1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coachTenureOfJohnThompsonJr Context triple: [Georgetown Hoyas men's basketball, coachTenureOfJohnThompsonJr, 1972–1999]
-
A.
headCoachTenure
chosen
Indicates the duration or period during which a specific individual serves as the head coach of a team or organization.
-
B.
endTimeOfTenureWithBostonCeltics
Indicates the date and time when an individual's tenure with the Boston Celtics came to an end.
-
C.
hiredAsHeadCoachYear
Indicates the year in which an individual was hired to serve as the head coach of a team or organization.
-
D.
endTimeAsHeadCoachOfChicagoBulls
Indicates the date and time when a person’s tenure as head coach of the Chicago Bulls ended.
-
E.
celticsCoachPlayer
Indicates that a specific coach has coached a specific player for the Boston Celtics basketball team.
- 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_69ab4ac019c8819094add11c46706e32 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd3f8a3888190889c537e6df07305 |
completed | March 7, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69abd0d19308819089ee942513d567a4 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.