Triple
T7699822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Conference (no divisions) |
E174460
|
entity |
| Predicate | standingsFormat |
P2673
|
FINISHED |
| Object | conference-based |
—
|
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: conference-based | Statement: [Western Conference (no divisions), standingsFormat, conference-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standingsFormat Context triple: [Western Conference (no divisions), standingsFormat, conference-based]
-
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.
standingsCriteria
Indicates the rules or factors used to determine the relative ranking or position of entities in a standings or leaderboard.
-
C.
competitionFormat
chosen
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
D.
leagueStandingDescribed
Indicates that a particular description or statement expresses or explains a team's position or ranking within a league's standings.
-
E.
tourFormat
Indicates the specific structure, style, or type of a tour associated with an entity.
- 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:03 p.m.