Triple
T24769771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1995 National League Championship Series |
E619688
|
entity |
| Predicate | roadTeamGame1 |
P124757
|
FINISHED |
| Object | Atlanta Braves |
—
|
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: Atlanta Braves | Statement: [1995 National League Championship Series, roadTeamGame1, Atlanta Braves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadTeamGame1 Context triple: [1995 National League Championship Series, roadTeamGame1, Atlanta Braves]
-
A.
roadTeam
chosen
Indicates that the specified team is playing as the visiting (away) team in a given game or event.
-
B.
decisiveGameRoadTeam
Indicates that the game was a decisive or series-clinching matchup in which the team playing on the road participated as the road team.
-
C.
recordGameTeam
Indicates recording or associating a specific game with a particular team in a data or tracking system.
-
D.
NLTeam
Indicates that there is a team relationship or membership association between entities, typically linking individuals to a specific team.
-
E.
team1
Indicates that the referenced entity is the first team or side participating in a competitive or relational context.
- 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a8dc8081909e2f4b65485a6786 |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:29 a.m.