Triple
T24688156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1987 National League Championship Series |
E611353
|
entity |
| Predicate | homeFieldTeam2 |
P135599
|
FINISHED |
| Object | San Francisco Giants |
—
|
NE NERFINISHED |
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: San Francisco Giants | Statement: [1987 National League Championship Series, homeFieldTeam2, San Francisco Giants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeFieldTeam2 Context triple: [1987 National League Championship Series, homeFieldTeam2, San Francisco Giants]
-
A.
homeTeam
Indicates that one entity is designated as the home team in a game, match, or sporting event involving another entity.
-
B.
locationTeam2Home
Indicates that the specified location serves as the home venue or home ground for the second team involved in the context.
-
C.
awayTeam
Indicates that an entity is designated as the visiting or non-home team in a competitive event or match.
-
D.
homeFieldForALTeam
Indicates that a particular stadium or ballpark serves as the designated home field for a specific American League baseball team.
-
E.
homeTeamForVenue
chosen
Indicates that a team is designated as the primary (home) team associated with a particular venue.
- 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_69e2c4d678b081908910f4271627a31a |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:19 a.m.