Triple
T435661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indianapolis Colts |
E10004
|
entity |
| Predicate | PeytonManningTenure |
P8422
|
FINISHED |
| Object | 1998–2011 |
—
|
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: 1998–2011 | Statement: [Indianapolis Colts, PeytonManningTenure, 1998–2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PeytonManningTenure Context triple: [Indianapolis Colts, PeytonManningTenure, 1998–2011]
-
A.
notableFormerQuarterback
Indicates that the subject was previously a quarterback and is recognized as notable or distinguished in that former role.
-
B.
nflTeamTenure
chosen
Indicates the period of time that an individual was a member of a specific NFL team.
-
C.
PatriotsQuarterback
Indicates that one entity serves as the quarterback for the New England Patriots football team.
-
D.
playedWithQuarterback
Indicates that one player participated on the same team at the same time as a specific quarterback, sharing game or practice play together.
-
E.
wonSuperBowlAsHeadCoachWith
Indicates that one entity served as the head coach of a team that won the Super Bowl with the other entity (the team) during that championship season.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef0b6e0c8190ad6a335ee804829c |
completed | Feb. 28, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69a2eddb98e081909efcf9f0a955a908 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.