Triple
T19767456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1899 Cleveland Spiders season |
E474794
|
entity |
| Predicate | winningPercentage |
P77799
|
FINISHED |
| Object | .130 |
—
|
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: .130 | Statement: [1899 Cleveland Spiders season, winningPercentage, .130]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winningPercentage Context triple: [1899 Cleveland Spiders season, winningPercentage, .130]
-
A.
allTimeWinningPercentage
Indicates the proportion of contests or games an entity has won over its entire recorded history, typically expressed as a percentage.
-
B.
regularSeasonWinningPercentage
chosen
Indicates the proportion of games a team or competitor wins during the regular season, expressed as a percentage of total regular-season games played.
-
C.
goalPercentage
Indicates the proportion of a goal that has been achieved relative to its total target.
-
D.
championshipWinRate
Indicates the proportion of championships won relative to the total number of championship opportunities or appearances.
-
E.
winningPercentageAsHeadCoach
Indicates the proportion of games a person has won while serving in the role of head coach.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65358fc3c8190867fea2a2c4e7594 |
completed | April 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.