Triple
T15731561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Brett |
E381356
|
entity |
| Predicate | batted300Career |
P119969
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [George Brett, batted300Career, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: batted300Career Context triple: [George Brett, batted300Career, yes]
-
A.
battedOver300Seasons
Indicates that a player achieved a batting average over .300 in one or more seasons.
-
B.
battedOver400Seasons
Indicates that the subject had one or more seasons in which their batting average exceeded .400.
-
C.
battedHomeRuns30PlusSeason
Indicates that the subject hit 30 or more home runs in a single season.
-
D.
battingMilestone
Indicates reaching a significant achievement or benchmark related to batting performance, such as a notable run total or record.
-
E.
leadingRunScorer
Indicates that the subject is the player who has scored the most runs (the top run-scorer) in a given match, series, tournament, or season.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fb61cb881908b158609c1ccfa1e |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e0094af5b481908ad51d5d7ba0c726 |
completed | April 15, 2026, 9:55 p.m. |
Created at: April 10, 2026, 4:46 a.m.