Triple
T17618520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1984 American League Championship Series |
E429646
|
entity |
| Predicate | ruleInEffect |
P114301
|
FINISHED |
| Object | designated hitter |
—
|
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: designated hitter | Statement: [1984 American League Championship Series, ruleInEffect, designated hitter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruleInEffect Context triple: [1984 American League Championship Series, ruleInEffect, designated hitter]
-
A.
rulesEffectiveUpon
chosen
Indicates that a set of rules becomes valid, applicable, or enforceable starting from a specified time, event, or condition.
-
B.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
-
C.
rulesDuring
Indicates that one entity holds authority or governance over another throughout a specified time period or interval.
-
D.
underRule
Indicates that one entity is governed, controlled, or subject to the authority, rules, or dominion of another entity.
-
E.
regulatingRules
Indicates that one entity establishes or enforces rules or standards that govern or control the behavior, operation, or conditions of 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d3489dc8190a619c58025dbb250 |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.