Triple
T49609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFC |
E975
|
entity |
| Predicate | competesFor |
P1375
|
FINISHED |
| Object | Super Bowl berth |
—
|
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: Super Bowl berth | Statement: [AFC, competesFor, Super Bowl berth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competesFor Context triple: [AFC, competesFor, Super Bowl berth]
-
A.
competesWith
chosen
Indicates that two entities are in rivalry or opposition, each striving to outperform or gain advantage over the other in the same domain or objective.
-
B.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
C.
competition
Indicates a relationship where two or more entities strive against each other to achieve a superior outcome, advantage, or reward.
-
D.
competitionLevel
Indicates the degree or intensity of competitive pressure or rivalry present in a given context or interaction.
-
E.
hasRelatedCompetition
Indicates that one competition is related to another competition in a meaningful way, such as being similar, connected, or associated within a shared context.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24b6c9eb88190b2fe85e427f4177a |
completed | Feb. 28, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69a24ac0fb088190b7a5e87817e8e747 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.