Triple
T30396771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | $100,000 infield |
E773239
|
entity |
| Predicate | hasPlayingStyleEra |
P162004
|
FINISHED |
| Object | Deadball Era |
—
|
NE NERFINISHED |
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: Deadball Era | Statement: [$100,000 infield, hasPlayingStyleEra, Deadball Era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayingStyleEra Context triple: [$100,000 infield, hasPlayingStyleEra, Deadball Era]
-
A.
playedWithEra
Indicates that an entity performed or was active during a specified historical or stylistic era.
-
B.
hasEraTheme
chosen
Indicates that something is associated with, characterized by, or themed around a particular historical or cultural era.
-
C.
hasApproximateEraOfPlayers
Indicates that two or more players are associated with roughly the same time period or era in which they were active.
-
D.
isBsideOfEra
Indicates that one entity is the B-side counterpart associated with a particular era of another entity (such as a primary release or period).
-
E.
playsInStyleOf
Indicates that one entity performs, creates, or behaves in a manner characteristic of another entity’s style.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 29, 2026, 8:02 p.m.