Triple
T26389255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Blue Nation |
E663366
|
entity |
| Predicate | supportsCoach |
P197225
|
FINISHED |
| Object | Kentucky Wildcats head basketball coach |
—
|
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: Kentucky Wildcats head basketball coach | Statement: [Big Blue Nation, supportsCoach, Kentucky Wildcats head basketball coach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCoach Context triple: [Big Blue Nation, supportsCoach, Kentucky Wildcats head basketball coach]
-
A.
requiresCoach
Indicates that one entity depends on or must have the involvement, guidance, or supervision of a coach in order for an action, process, or state to occur or be valid.
-
B.
basedInAsCoach
Indicates that a person holds a coaching position for an organization or team that is located in a specified place.
-
C.
isCoach
Indicates that one entity serves as the coach (trainer or instructor) of another entity.
-
D.
coachSince
Indicates that one entity has been serving as a coach for another entity starting from a specified point in time.
-
E.
involvesCoach
Indicates that a situation, event, or relationship includes a coach as an active participant or relevant party.
- F. None of above. chosen
Provenance (4 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
| PDg | Predicate description generation | batch_69fe7eb31b04819081be531fd9f8a78c |
completed | May 9, 2026, 12:24 a.m. |
Created at: April 26, 2026, 11:24 p.m.