Triple
T8218959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American League batting champion |
E192007
|
entity |
| Predicate | recordKeeping |
P41398
|
FINISHED |
| Object | maintained in MLB official record books |
—
|
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: maintained in MLB official record books | Statement: [American League batting champion, recordKeeping, maintained in MLB official record books]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordKeeping Context triple: [American League batting champion, recordKeeping, maintained in MLB official record books]
-
A.
recordKeeper
Indicates a relationship where one entity is responsible for maintaining, managing, or preserving official records or documented information about another entity or activity.
-
B.
recordHeld
Indicates that one entity possesses or maintains a particular record associated with another entity or context.
-
C.
recordStatus
Indicates the current state or condition of a record within a system or process (e.g., active, inactive, pending, or archived).
-
D.
recordHeldIn
chosen
Indicates that a record is stored, maintained, or kept within a particular location, system, or repository.
-
E.
recorded
Indicates that one entity captured, stored, or documented information, audio, video, or data about another entity or event.
- 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_69ca82c9a8ac81908b011c38698456e4 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb7772b76c8190b1952650c736eb91 |
completed | March 31, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69cb36af41e081909dee92b9bc4947f1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:45 p.m.