Triple
T9959911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mike Holmgren |
E195540
|
entity |
| Predicate | coachedPositionGroup |
P18810
|
FINISHED |
| Object | quarterbacks |
—
|
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: quarterbacks | Statement: [Mike Holmgren, coachedPositionGroup, quarterbacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coachedPositionGroup Context triple: [Mike Holmgren, coachedPositionGroup, quarterbacks]
-
A.
positionCoached
chosen
Indicates that one entity served as a coach for another entity in a specific position or role.
-
B.
coachingTeam
Indicates that one entity serves as a coach or coaching staff for a particular team.
-
C.
coachedAlongside
Indicates that two or more individuals served as coaches at the same time, typically for the same team, organization, or event.
-
D.
conferenceCoach
Indicates a person who provides guidance, training, or mentorship to participants in the context of a conference or similar professional gathering.
-
E.
positionGroup
Indicates a grouping relationship where multiple positions or roles are collectively associated or organized under a common group.
- 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_69ca82eaaa008190a54fa1a9f954b9ad |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb6d08fdc8190a77b9c97830035bc |
completed | April 2, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:46 p.m.