Triple
T484071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFC Championship |
E9834
|
entity |
| Predicate | hasPlayoffSeedingBasis |
P13509
|
FINISHED |
| Object | regular-season record |
—
|
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: regular-season record | Statement: [NFC Championship, hasPlayoffSeedingBasis, regular-season record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayoffSeedingBasis Context triple: [NFC Championship, hasPlayoffSeedingBasis, regular-season record]
-
A.
hasAutomaticPlayoffBids
Indicates that certain participants are guaranteed entry into a playoff competition without needing to qualify through regular selection or performance criteria.
-
B.
playoffQualification
Indicates that an entity has secured a position to participate in a postseason playoff competition based on qualifying criteria.
-
C.
usesPlayoffs
Indicates that a competition or league determines its final standings or champion through a postseason playoff format rather than solely by regular-season results.
-
D.
hasPlayoffMeetings
Indicates that the entities have faced each other in playoff competitions or postseason matchups.
-
E.
hasQualifyingRounds
Indicates that an event or competition includes preliminary qualifying rounds that participants must complete before advancing further.
- F. None of above. chosen
Provenance (4 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0ba310c81909645ef7e8a20b52f |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf48ec08190b85d07e194f99c49 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeba8a488190986cc7381332f783 |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.