Triple
T4404440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WHL regular season |
E93693
|
entity |
| Predicate | standingsCriteria |
P56058
|
FINISHED |
| Object | points |
—
|
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: points | Statement: [WHL regular season, standingsCriteria, points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standingsCriteria Context triple: [WHL regular season, standingsCriteria, points]
-
A.
hasStandings
Indicates that an entity possesses or is associated with a set of rankings, positions, or status levels within a competitive or comparative context.
-
B.
leagueStandingDescribed
Indicates that a particular description or statement expresses or explains a team's position or ranking within a league's standings.
-
C.
hadStandingsPublishedIn
Indicates that the standings or rankings associated with an entity were published in a particular source, venue, or medium.
-
D.
usesRegularSeasonStandingsFor
Indicates that one entity determines outcomes or decisions based on the regular season standings of another entity.
-
E.
currentStandingColumns
Indicates that certain columns are presently active, visible, or in use within a given context or layout.
- 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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b35488d5b8819087370dd77249aefb |
completed | March 13, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3509997208190933f167f7e20ccfa |
completed | March 12, 2026, 11:47 p.m. |
Created at: March 12, 2026, 11:28 p.m.