Triple
T29165765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1995 Major League Baseball season |
E739312
|
entity |
| Predicate | wildCardIntroducedPreviously |
P69146
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [1995 Major League Baseball season, wildCardIntroducedPreviously, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wildCardIntroducedPreviously Context triple: [1995 Major League Baseball season, wildCardIntroducedPreviously, 1994]
-
A.
introducedBefore
chosen
Indicates that one entity was introduced or presented earlier in time than another entity.
-
B.
laterReintroducedBy
Indicates that something previously removed, discontinued, or absent was brought back or reinstated at a subsequent time by a specified agent or entity.
-
C.
wasIntroducedInField
Indicates that something (such as a concept, method, or entity) was first presented or brought into use within a particular field or domain.
-
D.
isIntroducedInContextOf
Indicates that one entity is presented, mentioned, or brought into consideration specifically within the scope, situation, or circumstances defined by another entity.
-
E.
introducedAfter
Indicates that one entity was introduced at a later time or stage than another entity.
- 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_69f07cb6394c8190ab7842c48e699e2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f662d4efc88190a18d80abadc96faf |
completed | May 2, 2026, 8:47 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:49 a.m.