Triple
T405199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National League East |
E9367
|
entity |
| Predicate | hasChampionshipTitle |
P313
|
FINISHED |
| Object | National League East division title |
—
|
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: National League East division title | Statement: [National League East, hasChampionshipTitle, National League East division title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChampionshipTitle Context triple: [National League East, hasChampionshipTitle, National League East division title]
-
A.
hasChampionships
chosen
Indicates that one entity possesses or has won one or more championships associated with another entity.
-
B.
championshipRecognition
Indicates formal acknowledgment that an entity has won or holds a championship title in a given competition or domain.
-
C.
mastersTitles
Indicates that one entity holds one or more master's degree titles associated with another entity (such as an institution, field, or program).
-
D.
majorChampionshipWins
Indicates the number of major championship titles an entity has won.
-
E.
wonDivisionTitle
Indicates that an entity secured first place in its competitive division, earning the division championship title.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eca37fe881909802126952dfdd59 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e97066e8819083cc1b3a421b9650 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.