Triple
T32565166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1932 NFL Playoff Game |
E832341
|
entity |
| Predicate | spartansCoach |
P2169
|
FINISHED |
| Object | Potsy Clark |
—
|
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: Potsy Clark | Statement: [1932 NFL Playoff Game, spartansCoach, Potsy Clark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spartansCoach Context triple: [1932 NFL Playoff Game, spartansCoach, Potsy Clark]
-
A.
coachOf
chosen
Indicates that one entity serves as the coach (trainer or manager) of another entity, typically a person or team.
-
B.
offensiveCoach
Indicates that one entity serves as the offensive coach (responsible for directing the offense) for another entity, typically a sports team or player.
-
C.
playingCoach
Indicates a person who simultaneously serves as both a player and a coach for the same team or organization.
-
D.
featuredCoach
Indicates that a particular coach is highlighted or given special prominence within a specific context or collection.
-
E.
conferenceCoach
Indicates a person who provides guidance, training, or mentorship to participants in the context of a conference or similar professional gathering.
- 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:03 a.m.