Triple
T24971457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009 AFC Wild Card Game |
E624899
|
entity |
| Predicate | bengalsHomeFieldAdvantage |
P38899
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [2009 AFC Wild Card Game, bengalsHomeFieldAdvantage, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bengalsHomeFieldAdvantage Context triple: [2009 AFC Wild Card Game, bengalsHomeFieldAdvantage, Yes]
-
A.
bengalsSeed
Indicates the playoff seeding or ranking position assigned to the Bengals in a given season or tournament.
-
B.
homeFieldAdvantage
Indicates that one participant benefits from playing or operating in a familiar or home environment, gaining an advantage over the opponent.
-
C.
homeFieldAdvantageBasedOn
Indicates that the degree of home-field advantage is determined or influenced by the specified factor or condition.
-
D.
homeFieldAdvantageFor
chosen
Indicates that one entity benefits from playing or operating in its own familiar location or environment when facing the other entity.
-
E.
homeFieldAdvantageKnownFor
Indicates that a team, player, or venue is particularly recognized for performing better or having a notable advantage when playing at its home location.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 6:01 a.m.