Triple
T37544504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rex Ryan’s 3–4 attacking defense |
E933419
|
entity |
| Predicate | notableUsageTeam |
—
|
GENERATED |
| Object | Baltimore Ravens |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableUsageTeam Context triple: [Rex Ryan’s 3–4 attacking defense, notableUsageTeam, Baltimore Ravens]
-
A.
usedByTeams
chosen
Indicates that something (such as a tool, resource, or process) is utilized or employed by one or more teams.
-
B.
notableTeamType
Indicates that an entity is notably associated with a team of a specified type (e.g., national team, club team, or other team category).
-
C.
notableTeams
Indicates that there is a noteworthy association between an entity and one or more teams with which it is significantly connected or recognized.
-
D.
notableTeamOperated
Indicates that an entity is or was operated, managed, or run by a team that is considered notable or significant.
-
E.
notableRecipientTeam
Indicates that an entity has received a notable award, honor, or recognition specifically in the context of a particular team.
- F. None of above.
Provenance (1 batch)
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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.