Triple
T38210145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1892 Yale Bulldogs football team |
E1010515
|
entity |
| Predicate | coachRoleOf |
P188158
|
FINISHED |
| Object | Walter Camp as "Father of American Football" |
—
|
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: Walter Camp as "Father of American Football" | Statement: [1892 Yale Bulldogs football team, coachRoleOf, Walter Camp as "Father of American Football"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coachRoleOf Context triple: [1892 Yale Bulldogs football team, coachRoleOf, Walter Camp as "Father of American Football"]
-
A.
coachedRole
Indicates that one entity served as a coach for another entity in a specific role or position.
-
B.
coachOfTeamRole
chosen
Indicates that an individual serves in the role of coach for a specific team.
-
C.
coachSince
Indicates that one entity has been serving as a coach for another entity starting from a specified point in time.
-
D.
coachProfession
Indicates that one entity serves professionally as a coach in relation to the other entity.
-
E.
coachDescription
Indicates that one entity serves as a coach for another, typically providing guidance, training, or instruction.
- 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.