Triple
T24734618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1994 Major League Baseball season |
E618376
|
entity |
| Predicate | plannedWildCardImplemented |
P157059
|
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: [1994 Major League Baseball season, plannedWildCardImplemented, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedWildCardImplemented Context triple: [1994 Major League Baseball season, plannedWildCardImplemented, no]
-
A.
championshipGamePlanned
Indicates that a championship game has been scheduled or arranged to take place between competitors.
-
B.
implementedPlan
Indicates that a specific plan has been carried out or put into effect by an entity.
-
C.
plannedReplacement
Indicates that one entity is intended or scheduled to be replaced by another entity in the future.
-
D.
draftedInPlace
Indicates that an entity was formally written or composed at a specific location.
-
E.
futureStadiumProject
Indicates a planned or proposed stadium development that is intended to be built or realized in the future.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f410a25ab88190a72db43043c1f6ff |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f410a001788190a457e41f53aaf90c |
completed | May 1, 2026, 2:32 a.m. |
Created at: April 18, 2026, 4:03 a.m.