Triple
T11033902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National League pennant races |
E260826
|
entity |
| Predicate | usesRankingBy |
P53495
|
FINISHED |
| Object | win–loss record |
—
|
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: win–loss record | Statement: [National League pennant races, usesRankingBy, win–loss record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRankingBy Context triple: [National League pennant races, usesRankingBy, win–loss record]
-
A.
usesRank
Indicates that one entity applies or relies on a ranking or ordered level system associated with another entity.
-
B.
usesRankStructure
Indicates that an entity organizes its members or components according to a defined hierarchical rank structure.
-
C.
hasRankingFactor
chosen
Indicates that one entity contributes as a factor to determining the ranking or ordered position of another entity.
-
D.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
E.
selectionRankingEndPoint
Indicates the position or boundary in an ordered list at which a selection or ranking process concludes.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797e709648190adbb05197e15ff76 |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d7440087ac8190aef2e6f6b13b2635 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:25 p.m.