Triple
T4778364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 American League Championship Series |
E106108
|
entity |
| Predicate | team2PostseasonEntry |
P59264
|
FINISHED |
| Object | wild card |
—
|
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: wild card | Statement: [2014 American League Championship Series, team2PostseasonEntry, wild card]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: team2PostseasonEntry Context triple: [2014 American League Championship Series, team2PostseasonEntry, wild card]
-
A.
postseasonTeam
Indicates that a team participated in a postseason or playoff phase of a competition.
-
B.
visitingTeamRecordEnteringGame
Indicates the performance record (such as wins and losses) that the visiting team has accumulated prior to the start of the game.
-
C.
managedPostseasonAppearance
Indicates that a person served as the manager or head coach of a team during a specific postseason appearance.
-
D.
hasPostseasonAccess
Indicates that an entity is granted the right or eligibility to participate in postseason or playoff competitions.
-
E.
team2
Indicates that the second team involved in a competitive or collaborative context is associated with a given entity or event.
- 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_69bd43f3074c8190937e7b0a457fe9f1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd69237f80819090713ed62653fb75 |
completed | March 20, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69bd622be1388190ab5511b589c878c0 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd6922407481908565ed0b1dac2b30 |
completed | March 20, 2026, 3:34 p.m. |
Created at: March 20, 2026, 1:21 p.m.