Triple
T177192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FCS |
E3597
|
entity |
| Predicate | includesPostseasonIn |
P7451
|
FINISHED |
| Object | December |
—
|
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: December | Statement: [FCS, includesPostseasonIn, December]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPostseasonIn Context triple: [FCS, includesPostseasonIn, December]
-
A.
postseasonType
Indicates the specific kind of postseason competition or phase associated with an event or team.
-
B.
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.
-
C.
hasAutomaticPlayoffBids
Indicates that certain participants are guaranteed entry into a playoff competition without needing to qualify through regular selection or performance criteria.
-
D.
includesLeague
Indicates that an entity (such as a competition, organization, or system) contains or encompasses a specific league as one of its components.
-
E.
playoffAppearances
Indicates the number of times an entity (such as a team or player) has qualified for and participated in postseason playoff competition.
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a258fd278481908ad4498e03f38e2f |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a25669d99481908c5e82ba8641205a |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a258b30f6c8190be2181f30c40e04d |
completed | Feb. 28, 2026, 2:53 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.