Triple
T29237659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Working Man |
E741234
|
entity |
| Predicate | radioSuccessRegion |
P83283
|
FINISHED |
| Object | Cleveland |
—
|
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: Cleveland | Statement: [Working Man, radioSuccessRegion, Cleveland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radioSuccessRegion Context triple: [Working Man, radioSuccessRegion, Cleveland]
-
A.
radioSuccess
Indicates that an entity has achieved success or favorable outcomes in the context of radio broadcasting or radio-related activities.
-
B.
accessPointRegion
Indicates the geographic or spatial region within which a given access point is located or operates.
-
C.
broadcastRegion
Indicates the geographic area or market in which content is transmitted or made available for broadcast.
-
D.
radioFormatSuccess
Indicates that a particular radio format or programming approach has achieved success, such as strong performance or positive outcomes.
-
E.
successRegion
chosen
Indicates the geographic or contextual area within which a particular action, process, or outcome is considered successful.
- 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_69f0911dd6fc819097d1abb287016489 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66466747481909182bd6cf85d8eff |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:30 p.m.