Triple
T24305692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American League 1902 season |
E612527
|
entity |
| Predicate | postseasonPlayed |
P78194
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [American League 1902 season, postseasonPlayed, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postseasonPlayed Context triple: [American League 1902 season, postseasonPlayed, no]
-
A.
postseasonGamesPlayed
Indicates the number of games an entity has participated in during postseason or playoff competition.
-
B.
hasPostseasonEvent
Indicates that an entity is associated with or participates in a postseason event, such as playoffs or championships, following a regular season.
-
C.
madePostseason
chosen
Indicates that an individual or team successfully qualified for and participated in the postseason phase of a competition or league.
-
D.
postseasonPeriod
Indicates that a time span occurs during the postseason phase of a sports or competitive season, after the regular season has concluded.
-
E.
postseasonType
Indicates the specific kind of postseason competition or phase associated with an event or team.
- 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2922641bc81908fa3595941e60741 |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:30 a.m.