Triple
T9397678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ray Perkins |
E226385
|
entity |
| Predicate | headCoachPosition |
P42164
|
FINISHED |
| Object | successor to Bear Bryant at Alabama |
—
|
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: successor to Bear Bryant at Alabama | Statement: [Ray Perkins, headCoachPosition, successor to Bear Bryant at Alabama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headCoachPosition Context triple: [Ray Perkins, headCoachPosition, successor to Bear Bryant at Alabama]
-
A.
headCoachTo
chosen
Indicates that one entity serves as the head coach of another entity, such as a team or organization.
-
B.
headCoachFrom
Indicates that one entity serves as the head coach and originates from, or is affiliated with, the location or organization represented by the other entity.
-
C.
championCoachPosition
Indicates that a coach held the coaching position for a team that won a championship.
-
D.
headCoachInLeague
Indicates that a person serves as the head coach of a team that competes in the specified league.
-
E.
headCoachEnd
Indicates the point in time or event at which an entity’s role or tenure as a head coach comes to an end.
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51541020819097da2eb60be73760 |
completed | April 1, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:46 p.m.