Triple
T19128457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland Blue Stockings |
E468247
|
entity |
| Predicate | playedRules |
P6601
|
FINISHED |
| Object | baseball rules of the 19th century |
—
|
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: baseball rules of the 19th century | Statement: [Cleveland Blue Stockings, playedRules, baseball rules of the 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedRules Context triple: [Cleveland Blue Stockings, playedRules, baseball rules of the 19th century]
-
A.
playedUnderRulesOf
chosen
Indicates that an activity or game was conducted in accordance with a specified set of rules or regulations.
-
B.
playedCode
Indicates that an entity performed or executed a specific piece of code.
-
C.
eraPlayed
Indicates the historical or stylistic time period during which something (typically a work or performance) was played or took place.
-
D.
playedUnder
Indicates that one person participated as a player on a team or in a context where another person served as their coach or manager.
-
E.
inningsPlayed
Indicates the number of innings in which an entity (typically a player or team) has participated during a game or season.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3ceb5808190b3b53d9e8df3605a |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.