Triple
T25890815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chester Goode |
E652323
|
entity |
| Predicate | radioVersionName |
P159546
|
FINISHED |
| Object | Chester Proudfoot |
—
|
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: Chester Proudfoot | Statement: [Chester Goode, radioVersionName, Chester Proudfoot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radioVersionName Context triple: [Chester Goode, radioVersionName, Chester Proudfoot]
-
A.
radioVersionType
Indicates the specific type or category of a radio version associated with an item or entity.
-
B.
radioServiceType
Indicates the specific category or kind of radio service associated with or provided by an entity.
-
C.
radioSystem
Indicates that one entity functions as, or is equipped with, a radio communication system used for transmitting and/or receiving signals.
-
D.
radioReleaseDate
Indicates the date on which something (typically a song, program, or broadcast content) was first released or made available on radio.
-
E.
radioInterface
Indicates a relationship where one entity provides or defines the radio communication interface used by another entity for wireless connectivity or control.
- 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_69e7ab3c6cc081908de59bfcc28ec19d |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6037eab948190b1e16f6f0a8697cc |
completed | May 2, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 22, 2026, 8:21 a.m.