Triple
T2210315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFC East rivalry |
E50900
|
entity |
| Predicate | typicalGameSlot |
P30931
|
FINISHED |
| Object | prime time |
—
|
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: prime time | Statement: [NFC East rivalry, typicalGameSlot, prime time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGameSlot Context triple: [NFC East rivalry, typicalGameSlot, prime time]
-
A.
slot
chosen
Indicates a relationship where an entity is assigned or occupies a specific position, time, or opening within an ordered or limited set of available places.
-
B.
typicalGameLocation
Indicates the usual or characteristic place where a game is played or takes place.
-
C.
notableGameType
Indicates that a game is of a particular type or category for which the subject is especially well known or notable.
-
D.
traditionalGame
Indicates that the relationship involves playing, practicing, or being associated with a game that is rooted in longstanding cultural or historical traditions.
-
E.
videoGame
Indicates that one entity is a video game associated with, created by, or otherwise related to another entity.
- 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_69a88b06709c8190978fb2418470d1b6 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfce5abc8190b90b92e32045385d |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbdaa26d48190860c33fd464c4845 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.