Triple
T1861230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Division (AHL) |
E34815
|
entity |
| Predicate | usesStandingsMetric |
P29373
|
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: [Central Division (AHL), usesStandingsMetric, points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStandingsMetric Context triple: [Central Division (AHL), usesStandingsMetric, 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.
usesRegularSeasonStandingsFor
Indicates that one entity determines outcomes or decisions based on the regular season standings of another entity.
-
C.
usedInTeamStatisticsFor
chosen
Indicates that something (such as a metric, value, or record) is utilized in compiling or calculating statistical information for a specific team.
-
D.
bestLeagueFinish
Indicates the highest final position or ranking an entity has ever achieved in a particular league or competition.
-
E.
eligibleLeague
Indicates that an entity (such as a team or player) is qualified or permitted to participate in a particular league.
- 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_69a88600b2f88190bc09303e68ab517e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abb16c09e48190a345c95eab59fd87 |
completed | March 7, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69abafe02c3c819093a4744b476106ca |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.