Triple
T6778416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1994 Division Series |
E155616
|
entity |
| Predicate | firstSeasonActuallyPlayed |
P26144
|
FINISHED |
| Object | 1995 |
—
|
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: 1995 | Statement: [1994 Division Series, firstSeasonActuallyPlayed, 1995]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSeasonActuallyPlayed Context triple: [1994 Division Series, firstSeasonActuallyPlayed, 1995]
-
A.
firstSeasonDetermined
Indicates that the initial season associated with an entity has been identified or established.
-
B.
firstSeasonRecord
Indicates the performance or statistical record achieved by an entity during its first season of participation in a given context.
-
C.
firstSeasonBothFranchisesPlayed
Indicates the first season in which both franchises were active and played concurrently.
-
D.
firstPlayed
Indicates that one entity was the earliest or initial thing (such as a song, game, or media item) that another entity engaged with or played.
-
E.
firstYearPlayed
chosen
Indicates the year in which an entity (such as a person or team) first began participating in the specified activity or domain.
- 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2689d408190bc2c1ce4ae9c1b13 |
completed | March 27, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69c6d095dcac8190bb9b943f50a7f885 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:14 p.m.