Triple
T26471604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Division (OHL) |
E665913
|
entity |
| Predicate | hasSeasonalStandings |
P11178
|
FINISHED |
| Object | OHL regular season |
—
|
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: OHL regular season | Statement: [East Division (OHL), hasSeasonalStandings, OHL regular season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeasonalStandings Context triple: [East Division (OHL), hasSeasonalStandings, OHL regular season]
-
A.
usesRegularSeasonStandingsFor
Indicates that one entity determines outcomes or decisions based on the regular season standings of another entity.
-
B.
hasStandings
chosen
Indicates that an entity possesses or is associated with a set of rankings, positions, or status levels within a competitive or comparative context.
-
C.
seasonLedLeague
Indicates that, in a given season, the subject entity led the league in a particular statistical category or performance measure.
-
D.
usesSeasonResults
Indicates that something bases its outcomes, decisions, or operations on the results from a particular season.
-
E.
hasSeasonalRound
Indicates a recurring, seasonally patterned cycle of movements, activities, or resource use associated with an entity over the course of a year.
- 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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 27, 2026, 12:19 a.m.