Triple
T31676693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Zachary |
E808417
|
entity |
| Predicate | recordInvolved |
P192718
|
FINISHED |
| Object | single-season home run record |
—
|
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: single-season home run record | Statement: [Tom Zachary, recordInvolved, single-season home run record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordInvolved Context triple: [Tom Zachary, recordInvolved, single-season home run record]
-
A.
trapInvolved
Indicates that a trap is involved in, or plays a role in, the specified event or relationship between entities.
-
B.
constantInvolved
Indicates that a constant participates in or is directly involved in the specified relation, operation, or context.
-
C.
passInvolved
Indicates that an entity is involved in a passing action, either as the passer, receiver, or otherwise participating party.
-
D.
recordDetail
Indicates that one entity stores or documents specific information or attributes about another entity.
-
E.
frontInvolved
Indicates that an entity is directly involved in or associated with the front (e.g., front line, front-facing part, or leading edge) of another entity or situation.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
| PDg | Predicate description generation | batch_69fd28379d2c8190903ba228ee1cc756 |
completed | May 8, 2026, 12:03 a.m. |
Created at: April 30, 2026, 11:03 p.m.