Triple
T10783828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL Eastern Conference Championship Game |
E254398
|
entity |
| Predicate | isPostseason |
P17811
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NFL Eastern Conference Championship Game, isPostseason, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPostseason Context triple: [NFL Eastern Conference Championship Game, isPostseason, true]
-
A.
isPostseasonGame
chosen
Indicates that the game takes place during a postseason or playoff phase rather than the regular season.
-
B.
hasPostseasonEvent
Indicates that an entity is associated with or participates in a postseason event, such as playoffs or championships, following a regular season.
-
C.
isInauguralPostseason
Indicates that the postseason event or appearance is the first one ever held or participated in by the relevant entity.
-
D.
includesPostseasonIn
Indicates that a time period, schedule, or dataset explicitly encompasses postseason games or events in addition to the regular season.
-
E.
madePostseason
Indicates that an individual or team successfully qualified for and participated in the postseason phase of a competition or league.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d1b4bc8190871dd21265065705 |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.