Triple
T23625268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheyney State Wolves men's basketball |
E583444
|
entity |
| Predicate | notableEraCoach |
P550
|
FINISHED |
| Object | John Chaney |
—
|
NE NERFINISHED |
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: John Chaney | Statement: [Cheyney State Wolves men's basketball, notableEraCoach, John Chaney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEraCoach Context triple: [Cheyney State Wolves men's basketball, notableEraCoach, John Chaney]
-
A.
notableCoach
chosen
Indicates that one entity is a coach who is widely recognized or distinguished in relation to the other entity.
-
B.
notableEraTeam1
Indicates that the first team is notably associated with, or representative of, a particular historical era or period.
-
C.
coachingEra
Indicates the time period during which a particular coach is in charge of a team or individual.
-
D.
notableEraTeam2
Indicates that the second team is notably associated with, or prominent during, a particular historical era or period.
-
E.
notableAssistantCoaches
Indicates that the subject has assistant coaches who are particularly distinguished or noteworthy in their roles.
- 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b17c993c8190bf9ee3201869d240 |
completed | April 29, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:46 p.m.