Triple
T19767474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland Spiders |
E474794
|
entity |
| Predicate | homeGamesPlayedElsewhereIn1899 |
P137251
|
FINISHED |
| Object | most games on the road |
—
|
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: most games on the road | Statement: [Cleveland Spiders, homeGamesPlayedElsewhereIn1899, most games on the road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeGamesPlayedElsewhereIn1899 Context triple: [Cleveland Spiders, homeGamesPlayedElsewhereIn1899, most games on the road]
-
A.
homeGamesPlayedBy
Indicates the number or set of home games that are played by a particular team or player.
-
B.
homeGamesPlayedIn
Indicates the venue or location where a team’s home games are played.
-
C.
homeGamesPlayedOn
Indicates that the specified home team plays its home games on the given date, day, or at the specified venue.
-
D.
gamesOf
Indicates a relationship where one entity is the set, list, or collection of games associated with another entity.
-
E.
playedHomeGamesFrom
Indicates the time period during which a team or player hosted their home games at a particular venue.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:48 p.m.